AutoEntry API
AutoEntry is an AI-powered automated data entry platform used by accountants, bookkeepers, and small-to-medium businesses to capture invoices, receipts, bank statements, and supplier statements and publish them into accounting software. An unofficial API lets you programmatically pull captured documents, extracted line items, VAT codes, expenses, and publish status—and push documents in for capture and trigger publishing into Xero, Sage, QuickBooks, and other connected ledgers.
What is AutoEntry?
AutoEntry is an AI-powered automated data entry platform for accountants, bookkeepers, and small-to-medium-sized businesses. It captures financial documents—through its mobile app, desktop upload, or a dedicated email address—then uses proprietary OCR and machine learning to extract data with up to 99% accuracy, recognize VAT codes and account categories, and publish the results directly into accounting software. AutoEntry processes over 28 million documents annually across 210,000+ businesses globally.
Core capabilities include:
- Document capture (purchase/sales invoices, receipts, bank and credit card statements) with or without line-item detail
- Automatic VAT code and account category recognition that learns patterns over time
- Supplier statement reconciliation to match invoices against statements
- Expense and mileage management with assignment to users
- VAT grouping and reporting by period
- One-click publishing into Xero, Sage, QuickBooks, FreeAgent, KashFlow, ClearBooks, and SortMyBooks
Common data entities:
- Documents, Captures, Uploads, Inbox items
- Invoices, Receipts, Line items, VAT codes, Categories
- Bank and credit card statements, Transactions
- Supplier statements, Reconciliations, Suppliers
- Expenses, Mileage claims, Users, Companies/Clients
- Publish destinations and integration mappings to connected ledgers
The AutoEntry Integration Challenge
Practices and businesses rely on AutoEntry to feed clean transaction data into their ledgers, but automating around it programmatically is non-trivial:
- No public developer API: AutoEntry exposes no documented endpoints or developer portal, so all automation runs through the authenticated web app and mobile app
- Mobile- and email-first capture: Documents enter via app photos, desktop uploads, and a dedicated email address—channels that aren't built for headless ingestion
- Multi-company structure: Accountants and bookkeepers manage many client companies under one login, each with its own categories, VAT settings, and publish destination
- Asynchronous OCR: Capture, extraction, and verification happen on a delay, so polling and status tracking are required to know when a document is ready to publish
- Downstream coupling: Publishing depends on the connected ledger (Xero, Sage, QuickBooks, FreeAgent), each with its own mapping rules and error states
- Line-item nuance: Detailed invoices carry per-line VAT codes and account categories that must be preserved exactly to keep the ledger reconciled
How Supergood Creates AutoEntry APIs
Supergood reverse-engineers AutoEntry's authenticated web and mobile flows to deliver a resilient, programmatic API layer over your AutoEntry account—covering capture, extraction, and publish without a public developer portal.
- Handles username/password and MFA securely in a managed session
- Maintains session continuity with automated refresh and change detection
- Normalizes documents, line items, VAT codes, and categories into consistent JSON across all client companies
- Tracks asynchronous OCR and publish status so you know exactly when a document is captured, verified, and posted to the ledger
Use AutoEntry with AI agents: AutoEntry MCP Server →
Getting Started
- Schedule Integration Assessment
Book a 30-minute session to confirm your client companies, capture channels, and connected accounting software.
- Supergood Generates and Validates Your API
We deliver a production-ready AutoEntry adapter tailored to your account, categories, and publish destinations.
- Deploy with Monitoring
Go live with continuous monitoring and automatic adjustments as AutoEntry evolves.
API Endpoints
Authentication
/authenticateAuthenticate to an AutoEntry account using username/password or MFA and obtain a session token for downstream calls.
Documents
/documentsList captured documents across client companies with filters for type, status, company, and date range.
Documents
/upload_documentSubmit an invoice, receipt, or bank statement (image or PDF) for OCR capture and extraction.
Extraction
/line_itemsRetrieve extracted line items, VAT codes, and account categories for a captured document.
Publishing
/publishPublish a verified document into the connected accounting software (Xero, Sage, QuickBooks, and others).
Reconciliation
/supplier_statementsPull supplier statements and their reconciliation status against captured invoices.
Use Cases
Automate document capture into AutoEntry
- Push invoices, receipts, and bank statements into AutoEntry programmatically instead of mobile photos or email - Tag each document to the correct client company and capture profile - Track OCR status until extraction completes and the document is ready to verify
Sync extracted data into a data warehouse
- Pull captured documents, line items, VAT codes, and categories into a central warehouse - Stream expense and mileage data to spend-analytics and reporting tools - Reconcile supplier statements against captured invoices across all clients
Orchestrate publishing to connected ledgers
- Trigger one-click publishing into Xero, Sage, QuickBooks, or FreeAgent from your own workflow - Validate VAT codes and account mappings before posting to the ledger - Capture publish errors and route exceptions back to bookkeepers for review
Manage multi-client bookkeeping at scale
- Enumerate all client companies under one login with their categories and VAT settings - Monitor capture and publish volumes per client for capacity planning - Assign expenses and mileage to users and surface outstanding items
Technical Specifications
Authentication
Username/password and MFA handled in a managed session
Connectivity
Authenticated web and mobile app flows; no public AutoEntry developer API is required
Response format
Normalized JSON across documents, line items, VAT codes, categories, and publish status
Rate limits
Adaptive throttling tuned to your account to avoid AutoEntry-side limits
Session management
Automatic session refresh, MFA replay handling, and credential rotation
Data freshness
Near real-time reads of captured documents with polling for asynchronous OCR completion
Security
Encrypted credential vault, scoped access tokens, SOC 2-aligned controls, and audit logging
Webhooks
Event-style callbacks for capture complete, verification, and publish status changes
Latency
Sub-second reads on cached entities; multi-second waits while OCR and publishing complete
Throughput
Horizontally scaled workers sized to high-volume document capture across many client companies
Reliability
Retry, backoff, and idempotency keys for uploads and publish operations
Adaptation
Continuous monitoring of AutoEntry releases and connected-ledger integration changes
Frequently asked questions
AutoEntry does not publish a documented developer API or portal. Supergood builds an unofficial, production-grade API over your authenticated AutoEntry account so you can automate capture, extraction, and publishing programmatically.
AutoEntry connects to Xero, Sage (including Sage Business Cloud), QuickBooks, FreeAgent, KashFlow, ClearBooks, and SortMyBooks. The Supergood API can trigger publishing into whichever ledger your account is connected to.
Yes. Supergood enumerates all client companies in your account and normalizes their documents, categories, and VAT settings, so you can automate across an entire practice from a single integration.
Extracted line items, per-line VAT codes, and account categories are preserved exactly as AutoEntry captures them, so published transactions stay reconciled in the downstream ledger.
Capture and extraction run on a delay. The API tracks document status and exposes webhooks or polling so you know precisely when a document is captured, verified, and ready to publish.