Bills read for you, confirmed by you
Email, upload, e-invoice and scanned PDF all end as a draft bill with coding suggested from that vendor's history; nothing posts until a person confirms.
Capture supplier bills, match them to what you received, and pay safely.
Accounts payable takes bills in by upload, email, file or e-invoice, reads them with rules and AI, and checks each one for duplicates, risk, price and receipt before a person confirms it. Payment runs and vendor bank changes pass through an approval matrix with a second person and a step-up check, so money leaves only when it should.
Email, upload, e-invoice and scanned PDF all end as a draft bill with coding suggested from that vendor's history; nothing posts until a person confirms.
Differences between order, receipt and bill become exceptions with an owner and a deadline instead of emails.
A run goes to the authority matrix, then needs a second person's step-up release; the preparer can never release.
The most common payment fraud is a changed bank account; changes wait for a call-back, a second approver and a waiting period.
Incentive payouts become compliant self-billed invoices with country packs and agreement checks, issued once.
Search or filter. Planned items are labelled; everything else is available now.
A vendor master with the documents, terms and controls that stop payment fraud before it starts.
8 featuresBills arrive by upload, email, file, e-invoice or AI reading, and a person confirms every one.
12 featuresMatch each bill to what you ordered and received, and route every difference to an owner with a due time.
10 featuresPayment runs are prepared in payables and released through treasury, with four eyes at every step.
10 featuresTax deducted at source and information returns follow dated rules.
5 featuresFor dealers and partners paid from statements, payables raises the invoice the supplier would have raised.
7 featuresReconcile what suppliers say you owe with what you recorded, and see payables at a glance.
5 featuresPayables works beside an existing ledger, with AI preparing and phones for approval.
5 featuresIt prepares the work. A person confirms it.
The same four building blocks, specific to Accounts Payable.
Bills, vendor bank changes and payment run releases are requests to the shared authority matrix. The next step waits for approval, and another person applies it.
Payables reports and dashboards for the clerk, manager and controller.
Datasets
Dashboards
Payables resources and events for other systems, plus an inbound email target for bills.
/v1 resources: vendors, bills, bill imports, captures, payment proposals, vendor statements, withholding rules, self-invoices, bank change requests, aging
Events
Connectors
Vendors, open bills and history load through Migrate with open items tied by currency, count and aging bucket. Procurement-platform packs are not covered by the finance rows.
Bills, bill detail, vendors, payment runs, the exceptions queue, aging and the approvals list open on a phone; a bill waiting approval links straight to its request. Native phone app comes after the back office.
Orders and receipts feed the two- and three-way match.
Approved payment runs hand off to the payment factory; settlement comes back.
Posted bills, accruals and payments post to the ledger; open items tie to the control account.
Input tax, withholding and reverse-charge self-invoices post to the tax ledger.
Approved expense claims arrive as draft bills for reimbursement.
Dealer and partner payouts become self-billed invoices.
Receipt accruals and prepaid schedules from bill lines feed the close.
Bills, bank changes and payment releases run on the authority matrix.
No. AI reads and suggests coding; a person confirms every field and posts.
Changes need a call-back to a known contact, a second approver, a waiting period and, by default, a Workflow request. Two suppliers sharing one bank account also hold the bill.
No. The preparer cannot release, release needs a step-up check and a single-use token, and the run must first be approved through the authority matrix.
By default goods lines need a receipt to match. A tenant that does not receive goods can set the match policy to none.
PEPPOL BIS, UAE PINT, KSA ZATCA UBL and India IRN JSON. Whether a country accepts the format for your filing is a tax-adviser question.
Yes. Payables postings are kept here and sent to your existing accounting system.
The checksum and call-back controls are. Live verification through a bank or provider account is planned and needs that account.