Aureae Intake · Pre-launch

Invoices in. Checked, approved records out.

Aureae Intake is a document workflow for manufacturers. Claude reads each invoice, rule-based checks test the numbers, and a person approves the record before it’s exported to CSV, with Tally and ERP connectors later.

Workflow

Four steps, one record.

Every document moves through the same steps, and nothing leaves the system until a person has approved it.

  1. 01 / INTAKE

    Upload a document

    A PDF or scanned supplier invoice. Purchase orders, delivery challans and email forwarding are later scope.

  2. 02 / EXTRACT

    Claude reads it

    The Claude API reads the page, including tables and line items, and returns the fields in our record format.

  3. 03 / CHECK

    Rules test the numbers

    Deterministic checks recompute line amounts, subtotals, GST and totals, and flag gaps or conflicts.

  4. 04 / REVIEW & EXPORT

    A person approves

    Your team checks flagged fields against the source, corrects them, approves, then exports CSV.

Fields

What each record captures.

The draft field list for Indian GST invoices. Column names are the planned CSV headers, and may change as we test with manufacturers.

  • DOCUMENT

    Header

    • Document typeinvoice
    • Invoice / PO numberinvoice_no
    • Invoice dateinvoice_date
    • Place of supplyplace_of_supply
  • SUPPLIER & BUYER

    Parties

    • Supplier namevendor
    • Supplier GSTINgstin
    • Buyer namebuyer
    • Buyer GSTINbuyer_gstin
  • LINE ITEMS

    Each line

    • Descriptionitem
    • HSN / SAChsn
    • Quantity and unitqty, unit
    • Rate and amountrate, amount
  • TAX

    GST breakdown

    • CGST rate and amountcgst
    • SGST rate and amountsgst
    • IGST rate and amountigst
    • Cess, if anycess
  • TOTALS

    Amounts

    • Taxable valuetaxable_value
    • Total taxtax_total
    • Round-offround_off
    • Invoice totalinvoice_total
  • REVIEW

    Record status

    • Flags raisedflags
    • Fields correctedcorrections
    • Approved byapproved_by
    • Approved atapproved_at

Validation

Checks before anyone approves.

Claude proposes the values; the arithmetic is verified by rules, not by the model. Checks marked Prototype are in scope for the first build.

CheckWhat it testsStage
Required fieldsVendor, GSTIN, invoice number, date and total are present; anything missing is flagged.Prototype
Line arithmeticQuantity × rate matches each line amount, within rounding.Prototype
SubtotalLine amounts add up to the taxable value.Prototype
Tax mathsCGST + SGST, or IGST, match the stated rates and the taxable value; the grand total adds up.Prototype
GSTIN structureFormat and check-digit test on the GSTIN text. This is not a government registry lookup.Prototype
Intra- or inter-stateCGST/SGST versus IGST is consistent with the supplier’s state code and the place of supply.Prototype
Uncertain valuesHandwritten corrections, unclear scans and low-certainty fields are sent to a person first.Prototype
DuplicatesThe same supplier GSTIN and invoice number already approved before.Later
PO matchInvoice lines compared with the purchase order’s items, quantities and rates.Later

Human review

People approve. Software assists.

The review screen puts the source document next to the proposed record, so your team reviews an invoice instead of retyping it.

See the sample review screen

  • Side by side. The document and its fields on one screen.
  • Flags first. Failed checks and uncertain values are shown at the top, with the reason.
  • Edit with history. Corrections keep the original value, so changes can be traced.
  • Explicit approval. Records export only after someone approves them, and the approver and time are kept with the record.
  • Reject or hold. Documents that can’t be resolved stay out of the export.

Export

Data your accounts team can use.

CSV comes first because most accounting and ERP tools can import it. Connectors follow what early-access customers actually use.

  • CSVPrototype

    Line-level CSV

    One row per line item, with invoice fields repeated, ready for spreadsheets and imports.

  • TALLYLater

    Tally-ready import

    Export shaped for Tally imports, scoped with customers who use Tally.

  • ERPLater

    ERP connectors

    Direct connections, prioritised by the systems early-access customers run.

Planned CSV columns · sample rowSample data
vendor,gstin,invoice_no,invoice_date,item,hsn,qty,unit,rate,amount,cgst,sgst,invoice_total
Sample Traders,27AAAAA0000A1Z5,ST/26-27/0142,2026-10-06,MS flat bar 40x6 mm,7216,250,kg,62.00,15500.00,1395.00,1395.00,22302.00

Fictional supplier and GSTIN. Illustrates the intended format; not output from a live system.

Where Claude fits

Built on the Claude API by Anthropic.

Claude does the reading. Rules do the maths. People make the decision.

  • Document reading. Claude interprets printed and scanned invoices, including multi-line tables, units and tax blocks.
  • Structured extraction. Claude returns fields in our record schema rather than free text, so every record has the same shape.
  • Uncertainty surfaced. Values that are unclear on the page are marked for review instead of guessed silently.
  • Independent checks. Totals and tax are recomputed by our own rules, so a misread number gets caught.
  • No auto-posting. Nothing is exported until a person approves it.

Markets

India first. The US next.

The first version is designed around Indian GST invoices: GSTIN, HSN/SAC codes, CGST, SGST and IGST, and Indian number and date formats. After that, we plan to support US manufacturers, with US invoice layouts and sales-tax fields.

Document handling. This website doesn’t accept documents. Prototype testing uses synthetic or permissioned invoices, and before any early-access customer shares documents we’ll agree in writing how they are stored, kept and deleted.

Early access

Want Aureae Intake for your invoices?

Tell us which documents your team handles, roughly how many a month, and which software you use. We’ll reply about your workflow and future early access.

The button opens your email app. Please don’t send confidential documents; a short description of your workflow is enough.