Automated supplier invoices
Invoices arrive by email, AI reads them, your rules match them to the purchase order and the delivery slip, and a person approves in one click before they reach accounting.
Automate Acomba with AI
Official Acceo developer
Your Acomba stays on your server. A small service installed beside it gives it a safe API: the brain reads your customers, suppliers and general ledger there, and writes invoices and payments that are already checked.
What we connect to Acomba
- Customers and receivablesReads · Writes
Search, record and balance of each customer, new customers, statements and receivables aging.
- Invoices and paymentsReads · Writes
Sales invoices with their lines, GST and QST computed by Acomba; cancelling an unpaid invoice; payments received, applied to invoices.
- Suppliers and their invoicesReads
Supplier records, supplier invoices and credits, payables aging.
- Products and inventoryReads
Product codes, prices, quantities on hand, on order and available.
- General ledgerReads
Chart of accounts, trial balance and monthly reports.
Possibilities
What we can also connect through Acomba's API, depending on your project.
- Bank reconciliation prepared from statements
- Follow-ups on overdue receivables
- Customer orders created from emails
- Sales and margin dashboard
How it connects
1
Simulation first
Every write starts in simulation: you see what would be written, and nothing is. Then last month's data, one team, and finally everyone.
2
Acomba stays the ledger
Your official numbers stay in Acomba. The brain computes beside it and writes back clean, approved data.
3
Your own access
The integration uses access in your name, limited to what it does, that you can remove in one click. The code is in your repository.
Frequently asked questions
Does Acomba have an API?
Not an open web API: Acomba is installed on the company's server and programmed through its SDK. We install a Windows service beside it that talks to Acomba's SDK and offers a protected REST API: one key per calling system, limited to reading or writing.
Does my data leave my server?
Only what the work needs. Acomba and its company file stay on your server; the service answers authorised calls, through an encrypted tunnel, and every write is logged with who made it and when.
What if a write fails or is sent twice?
Nothing is written twice: each write carries a unique id, and a second request returns the first result. A write Acomba refuses comes back with a clear message; nothing is half written.
Do I need another version of Acomba?
No. The service checks at each opening that your version of Acomba is compatible, and refuses to write until it is.
Let's talk about your Acomba
A conversation with a senior architect: your data, your rules, and what a first sprint would deliver.
Talk with an expertWorking code every week
Every sprint ships something your team uses.
You own everything
The code, the database, the servers. No licence.
Rules you can check
Your rules written in code, every decision logged.
Fixed price, stop anytime
One feature a week, no long-term contract.