Sign in Start free trial
Finance

Accounts Payable

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.

60 features available 2 planned 8 capability areas
Highlights

What stands out

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.

Three-way match with owners and due times

Differences between order, receipt and bill become exceptions with an owner and a deadline instead of emails.

Payment release with four eyes

A run goes to the authority matrix, then needs a second person's step-up release; the preparer can never release.

Bank changes need a call-back

The most common payment fraud is a changed bank account; changes wait for a call-back, a second approver and a waiting period.

Self-billing for dealers and partners

Incentive payouts become compliant self-billed invoices with country packs and agreement checks, issued once.

Capabilities

Every feature, in one list

Search or filter. Planned items are labelled; everything else is available now.

Vendors and bank details

A vendor master with the documents, terms and controls that stop payment fraud before it starts.

8 features
  • Vendor masterA vendor links a party from the shared contacts master to a legal entity, with currency, payment terms, withholding settings and tax documents.
  • Vendor tax documents and bank accountsKeep tax documents and bank accounts on the vendor record, with changes controlled as described below.
  • Payables set-up per entityTurn payables on for an entity: posting accounts by role, voucher numbering, terms and match tolerances.
  • Bank-change controlNew bank details become active only after a call-back to a known contact, a second approver and a waiting period; the payment hold is released only when the change is approved.
  • Bank change through WorkflowThe bank change is also a request to the authority matrix; the approval step waits for it, and withdrawing the request rejects the change and releases the hold.
  • Vendor readiness checkSee what is missing before a vendor can be paid: tax document, bank account, terms.
  • Block a vendor AI can block a vendor on request but can never unblock one; only a person can.
  • Live bank-account verificationPlannedIBAN and penny-drop checks and payee-name matching through a bank or verification provider. The checksum validation and the call-back control already run; the live provider call is not connected.

Capture and bill entry

Bills arrive by upload, email, file, e-invoice or AI reading, and a person confirms every one.

12 features
  • Bill entryEnter a bill as a draft with lines, tax, coding and attachments, check it and post it.
  • Upload and email-in captureEach entity can have an inbound address; files that arrive become captures waiting for a clerk.
  • File scan before readingEvery uploaded file goes through the vault's scan first; an infected file is quarantined and never read.
  • Rules-based readingInvoice number, date, totals and vendor are read by rules, with a confidence per field.
  • AI reading of scanned billsScanned PDFs and images are read by the platform's multimodal AI model, cheap model first with one escalation, with per-field confidence. A person confirms every field.
  • Coding from vendor historySuggested accounts and dimensions come from how that vendor was coded before.
  • Confidence threshold and flagged fieldsFields below the confidence you set are flagged for the clerk.
  • Inbound e-invoicesStructured supplier e-invoices (PEPPOL BIS, UAE PINT, KSA ZATCA UBL, India IRN JSON) become draft bills without retyping, with totals checked and unsafe files refused. A known supplier drafts at once.
  • Bill import batchesBring in many bills at once from a file, a scanning service or another system, checked against control totals.
  • Expense intakeEmployee expense claims arrive as draft bills for reimbursement.
  • Reverse-charge self-invoicesWhen posting a bill produces reverse-charge output tax, an RCM self-invoice is issued automatically in its own numbered series, and can be switched off by policy.
  • Capture funnel by channelSee how many bills arrive by each channel, how many were read by AI and with what confidence.

Matching and exceptions

Match each bill to what you ordered and received, and route every difference to an owner with a due time.

10 features
  • Two-way matchCompare bill lines with the purchase order snapshot, using tolerance templates for price and quantity.
  • Three-way match with receiptsRecord goods receipts and service receipts against an order and match the bill to order and receipt. By default goods lines need a receipt; set the policy to none if you do not receive goods.
  • Receipt controlsReceipts are never over-received; a reversal needs a reason and cannot go below what has been billed.
  • Exceptions and holds queueEvery bill on hold appears with its reason, owner and due time (default 48 hours), with mine and overdue views.
  • Resolution codesA hold is resolved by a person with a fitting code; a released duplicate or risk hold stands.
  • Duplicate detectionLook-alike invoice numbers are folded (O and 0, I and 1, leading zeros, transposed digits), scored and held. A one-character difference is not treated as similar, because vendors number in sequence.
  • Fraud and risk signalsStrong signals hold the bill: a bank account shared with another supplier, an outlier amount, a future date or a high-risk vendor. Advisory signals show a warning: a new vendor, a recent bank change or a round amount.
  • Bill approvalsBills are routed by amount, vendor and GL account on the authority matrix; the creator cannot approve a bill routed by account.
  • Bills through WorkflowBills, vendor bank changes and payment releases appear in one decisions list with where each stands.
  • GRNI accrualGoods received and not invoiced are accrued at period end, posted by another person and auto-reversed.

Payments

Payment runs are prepared in payables and released through treasury, with four eyes at every step.

10 features
  • Payment proposals and runsBuild a proposal of due items, group them into a run with instructions and a payment file.
  • Release with step-upAuthorising a run needs a step-up check and a single-use token, and the preparer can never be the releaser.
  • Run goes through the authority matrixThe release is a request to the matrix; authorise and the payment effect wait for an approved request matching the run's exact payees, amounts and banks.
  • Payment digestThe releaser sees a digest of what will be paid before authorising.
  • Take an item out of a draft runRemove a bill from a draft payment run before it is released.
  • Early-payment discountsWhen vendor terms carry a discount, items still open within the discount days are paid net, with the discount posted to a discount-received account.
  • Dynamic discountingOffer vendors early payment for a discount rate; off by default. A person records the vendor's answer.
  • Advances and prepaymentsPay a supplier in advance and apply it, or a vendor credit, to the bill when it arrives.
  • Pay file from another sourceA pay file arrives in payables as a draft payment proposal built by an approver, with refusals explained in words; release stays payables' own four-eyes step, and paid and returned status goes back.
  • Payments through the treasury factoryApproved runs hand off to the treasury payment factory for payment files and release.

Withholding and tax

Tax deducted at source and information returns follow dated rules.

5 features
  • Withholding on paymentIndia TDS and US 1099 reportable payments are handled at payment time with cumulative thresholds and rules kept as dated data.
  • CertificatesWithholding certificates are tracked per vendor.
  • US information return totalsReportable payments are totalled by year and box, ready for year-end returns. Electronic filing to the tax authority is a separate, unbuilt step.
  • Input tax postingInput tax and withholding post to the tax ledger.
  • 1099 electronic filing and TIN matchPlannedFiling and TIN matching with the tax authority needs government access that is not yet connected.

Self-billing and recipient-created invoices

For dealers and partners paid from statements, payables raises the invoice the supplier would have raised.

7 features
  • Self-billing from incentive payoutsPartner payouts from the incentive hub become self-billed invoices inside the agreement window, with its own series and a partner copy; blocked requests are listed with a retry.
  • Recipient-created tax invoicePayables raises the self-billed invoice from a published statement under the dealer's agreement, issued once, with a draft bill to post.
  • Supplier may not also invoiceA supplier bill for the same dealer, period and amount is refused while the self-billed invoice stands.
  • Credit note and supersedeA revised statement produces a credit note and a new invoice; an issued invoice is never edited.
  • Country packsPacks for Australia, New Zealand, the UK and the EU are effective-dated data showing their conditions and wording, marked awaiting counsel review until reviewed. An invoice from a supplier whose pack is unreviewed waits for a second person.
  • Supplier registration checksA check port for ABN, NZBN or GST, UK VAT and EU VIES; a lapsed registration blocks new invoices. Live registry accounts are not yet connected.
  • Agreement renewal in the portalDealers renew agreements through the portal with recorded evidence; expiry alerts go out at 60, 30 and 7 days.

Vendor statements and reporting

Reconcile what suppliers say you owe with what you recorded, and see payables at a glance.

5 features
  • Vendor statement reconciliationImport a vendor statement, reconcile it to your open items and have a person sign it off.
  • Payables agingWhat you owe each vendor grouped by days past due, as at any date.
  • Payables report packAging, open items, bill register, holds, payment proposals, withholding deducted and days payable outstanding, plus four more reports.
  • AP clerk and controller dashboardsDashboards show overdue holds, captures by channel and bills waiting for approval.
  • Bank-change registerA register of bank changes that never contains an account number.

Standalone, AI and phone

Payables works beside an existing ledger, with  AI preparing and phones for approval.

5 features
  • Payables without the general ledgerKeep payables postings here and send them to your existing accounting system.
  •  AI on every payables actionEvery screen action has a  AI action: record receipts, assign exceptions, prepare accruals, recheck a bill, create purchase order snapshots, capture and coding.
  • Capture and coding agentA built-in agent reads and codes bills under the AI control tower with a kill switch, a policy and a meter.
  • Phone approvalBills, vendors, payment runs, the exceptions queue, aging and the approvals list open on a phone; a bill waiting for approval links to its request.
  • Public API, events and importsPayables resources, events and vendor and bill imports for other systems.
Assistant

What  AI prepares here

It prepares the work. A person confirms it.

  • Read a bill and suggest coding for a person to confirm
  • Record a goods receipt
  • Assign an exception to an owner
  • Prepare an accrual run for a person to post
  • Recheck a bill against its order and receipt
  • Remove an item from a draft payment run
  • Create a purchase order snapshot
  • List decisions waiting on payables
  • Draft a vendor record or add a tax document
  • Run or clone a report pack
Inside every hub

Workflow, reporting, integration, migration

The same four building blocks, specific to Accounts Payable.

Workflow

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.

  • A bill above the approval band goes to the AP manager before it posts
  • A vendor bank change needs a call-back and a second approver, then a waiting period
  • A payment run is released by a payment approver and a treasurer with step-up
  • A bill routed by GL account cannot be approved by its creator

Reporting and analytics

Payables reports and dashboards for the clerk, manager and controller.

Datasets

Bill registerOpen itemsBill holds with owner and overduePayment proposalsWithholding deductedCaptures by channel and methodBank changesBills waiting approval

Dashboards

AP clerk dashboardPayables manager dashboardController dashboard

Integration

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

bill postedbill releasedpayment sentpayment settledreceipt recordedexception assignedaccrual postedcapture draftedself-invoice issuedself-bill blockedstatement reconciled

Connectors

Inbound e-invoice formats: PEPPOL BIS, UAE PINT, KSA ZATCA UBL, India IRN JSONInbound email address per entity for billsPayment hand-off to the treasury payment factory

Migration

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.

  • SAP S/4HANA, ECC, Business One and ByDesignavailable (MG-22 ON TST, verified 2026-11-04; fixture-tested.)
  • Oracle Fusion Cloud ERP, E-Business Suite, JD Edwards and PeopleSoftavailable (MG-23 ON TST, verified 2026-11-05; fixture-tested.)
  • NetSuite, Dynamics 365 and Sage familyplanned (MG-24 BUILT; ON TST once its deploy is verified.)
  • QuickBooks Online and Desktop, Tally, Xero, Zoho Booksplanned
  • Open AR, AP and bank items for any ERP sourceplanned (MG-FIN-02 OPEN (batch MG-28); the reconciliation ties (MG-REC-02) are ON TST.)
Mobile

On the phone

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.

Who uses it

AP clerkAP managerControllerBuyerTreasurer and payment approverDealer or partner (portal)

Industries

  • Projects and services firms with many supplier invoices
  • Groups needing country-specific supplier e-invoicing (India, UAE, Saudi Arabia)
  • Channel businesses paying dealers and partners from statements (self-billing packs for Australia, New Zealand, the UK and the EU)
Questions

Frequently asked

Does  AI post bills?

No.  AI reads and suggests coding; a person confirms every field and posts.

How does  AI protect against bank-detail fraud?

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.

Can a clerk release a payment run?

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.

Do we have to receive goods before paying?

By default goods lines need a receipt to match. A tenant that does not receive goods can set the match policy to none.

Which e-invoice formats can we receive?

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.

Can we pay from payables while keeping the books elsewhere?

Yes. Payables postings are kept here and sent to your existing accounting system.

Is bank-account verification included?

The checksum and call-back controls are. Live verification through a bank or provider account is planned and needs that account.

See Accounts Payable on  AI

Talk to us