Accounting

Availableapp.erp.io/accounting/bills

Bills and vendors

A supplier invoice arrives as a PDF. An agent reads it, a person confirms it, and it becomes a bill with a due date.

Entry
Upload, email, or manual
Extraction
AI proposes fields
Approval
Before payment
Payment
Recorded, not executed

From PDF to bill

The document arrives

Uploaded, or forwarded to the module's intake address.

An agent extracts the fields

Vendor, invoice number, date, due date, total, tax, and line detail where the layout allows.

A person confirms

This is the step that never goes away. Extraction is a first draft, reviewed field by field — the agent is a reviewer of its own reading, not an authority.

It becomes a bill

Posted to payables with the accounts and dimensions you chose.

It is approved

If your workflow requires approval before payment.

It is paid and reconciled

The payment is recorded here and matched to the bank line when it clears.

app.erp.io/accounting/bills
Bill — Meridian Supplies

Extracted from PDF · confirm before posting

RejectConfirm and post
Confirm and post
A bill under review. Extracted values on the right; the person confirms each one.

What extraction gets right and wrong

FieldReliabilityWatch for
TotalHighCredit notes, where the sign matters.
VendorHighA trading name that differs from the registered name.
DatesGoodAmbiguous formats on international documents.
TaxGoodMixed rates on one document.
Line detailVariableUnusual layouts, multi-page tables.
The right expense accountA guessIt is proposed from your history, which is a good prior and not a fact.
The check is field-level, not document-level

Confirming a bill means confirming its fields, not glancing at the total. A total that is right with a tax split that is wrong still posts a wrong entry, and it is the sort of error that survives until a return is prepared.

Vendors

A vendor record holds the details you need to pay them and the history of what you have. Extraction matches incoming documents against existing vendors, and creates one when it does not recognise the name — which is worth reviewing occasionally, because two records for the same supplier split their history and their ageing.

What this does not do

Payments are recorded, not executed

Nothing here moves money. You pay through your bank; the module records that you did.

No purchase orders

There is no PO object and therefore no three-way match against a receipt.

No approval matrix

Approval is a step, not a configurable ladder with thresholds and delegation.

No supplier portal

Vendors cannot log in to see what you owe them.

No automated payment runs

There is no batch payment file generation.

Questions

Can bills be emailed straight in?

Yes, to the module intake address. They arrive as documents awaiting extraction.

What if a supplier sends a credit note?

It is recorded as a negative bill and offsets in ageing.

Can two people approve?

Approval is recorded per bill with who did it. There is no enforced dual approval.