Agents that post to your ERP and show their work
Vaku drafts invoices, journals, purchase orders and close checks inside Oracle Fusion and Dynamics 365. Every entry is validated against your ledger and waits for the approvals you already have.
Runs inside Oracle Fusion Cloud and Microsoft Dynamics 365
| Account | Description | Debit | Credit |
|---|---|---|---|
| 6410-210-000 | Rent expense, Dubai HQ | 48,000.00 | |
| 2240-000-000 | Accrued liabilities | 48,000.00 |
One agent per task your team already does
Each agent knows the fields, validations and approval paths for one transaction type. Admins choose who gets which.
Day-to-day postings across payables, receivables, cash and order-to-cash.
- AP invoice
- Creates supplier invoices with lines, tax and GL coding.
- “Create an AP invoice for ABC Ltd, $5,000, NET30”
- Invoice ageing
- Reports open invoices by age bucket and supplier.
- “Show invoices overdue more than 30 days”
- Supplier setup
- Creates suppliers with sites, BU assignments and terms.
- “Create supplier Acme Inc, USA, payment terms NET45”
- Supplier ageing
- Ranks suppliers by outstanding balance.
- “List the top 10 suppliers by outstanding balance”
- Journal entry
- Drafts and posts balanced GL journals.
- “Post a journal: debit Cash $1,000, credit Sales $1,000”
- AR receipt
- Records customer receipts and applies them to invoices.
- “Apply a $500 receipt to customer XYZ invoice INV-001”
- Customer setup
- Creates customer accounts with billing terms.
- “Create customer Globex Corp, billing USD, NET30”
- Sales order
- Books sales orders with lines and ship dates.
- “Book an order for ABC Corp: 10 units of AS54888 at $250”
- Bank transfer
- Moves funds between internal bank accounts.
- “Transfer $50,000 from Corporate USD to Operations USD today”
- Bank balance
- Returns the latest balance for an account.
- “Show the latest balance of the Corporate USD account”
From request to posted entry
- 1
Connect your ERP
We register an integration user in Oracle Fusion or Dynamics 365 with the same roles your clerks have. No data warehouse, no sync jobs.
- 2
Assign agents by role
Your admin decides which people can run which agents. An AP clerk sees invoice agents; a controller also sees close and variance.
- 3
Ask in plain language
The agent drafts the transaction, looks up suppliers, accounts and periods, and asks only for what it couldn't infer.
- 4
Review, then submit
Nothing posts until the person confirms. Submissions go through your ERP's own approval rules and appear in its audit trail.
Built for the audit, not around it
The controls your auditors ask about on day one.
- Your ERP stays the system of record
- Agents call the ERP's published APIs as a named integration user. We don't keep a shadow ledger.
- Access follows roles
- Members only see the agents they're assigned. Admins manage users and agents per tenant; developers never see tenant data by default.
- Every turn is logged
- Prompts, the agent's lookups and the final payload are kept with the user and timestamp for audit.
- Data stays in region
- Tenants are pinned to the United States, European Union, UAE or Saudi Arabia at creation.
- Encrypted throughout
- TLS 1.2+ in transit and AES-256 at rest. ERP credentials are held in a managed key vault.
- SOC 2 Type II
- Audit in progress. We share the current controls matrix under NDA.
See it on your own ledger
In a 30-minute call we connect to a sandbox of your ERP and run two of your real transaction types end to end.
Prefer email? Write to karthikk@vakuai.com