Bookkeepers & accounts payable
Supplier invoices into your ledger, without a parser per supplier
Every supplier formats their invoice differently, and the ones who do not change it eventually will. If you are keying invoice totals in by hand, or maintaining a parser template per supplier, the work never actually finishes — it just moves.
Fieldcast takes the field names you want with each request. A new supplier with a layout nobody has seen before goes through the same call as the ones you already handle. Nothing to configure per vendor.
What the call looks like
The fields below are an example for this use case. Yours can be any names you like, up to 40 per call.
{
"fields": [
"supplier_name",
"invoice_number",
"invoice_date",
"due_date",
"net_amount",
"vat_amount",
"gross_amount",
"currency",
"po_number",
"payment_terms"
]
}And what comes back:
{
"supplier_name": "ACME SUPPLIES LTD",
"invoice_number": "INV-2026-0431",
"invoice_date": "2026-08-14",
"due_date": "2026-09-13",
"net_amount": 452.5,
"vat_amount": 90.5,
"gross_amount": 543.0,
"currency": "GBP",
"po_number": null,
"payment_terms": "Net 30"
}Why the details matter here
It says null instead of guessing
There was no purchase order number on that invoice, so po_number came back null. In bookkeeping a missing value is a queue item; a confidently wrong total is a reconciliation problem you find three months later.
Totals arrive as numbers
452.5, not "452,50 GBP". No thousands separators, no currency symbols glued to the figure, no locale guessing before it reaches your ledger.
Dates arrive as ISO-8601
2026-08-14 whether the invoice said 14 August 2026, 14/08/2026 or 08/14/2026. The ambiguity is resolved before it becomes a wrong due date.
What it does not do
- It does not read scanned or photographed invoices — PDF and text only, no OCR yet.
- It does not push into Xero, QuickBooks or Sage. It returns JSON; the posting is your code.
- It does not do three-way matching or approval routing.
- It is not a certified system of record. Validate values before they hit your books.
Listed plainly so you find out now rather than after integrating.
Questions
What happens when a supplier changes their invoice layout?
Nothing on your side. There is no stored template tied to that supplier, so a redesigned invoice goes through the same request as before.
Can I get line items, not just totals?
You can ask for a field like line_items and it will be returned, but structured repeating rows are the weakest part of any extraction system. Test it against your own invoices on the free tier before you depend on it.
Is it accurate enough for accounting?
On a ten-field invoice test, live in production, all ten fields were correct. That is one document, not a benchmark. The free tier is 50 extractions a month specifically so you can measure it on your own invoices instead of trusting that number.
Test it on your own documents
Free tier is 50 extractions a month, no card, no sales call. That is deliberately enough to check accuracy on real files before you commit to anything.
Read the quickstart