Payvance — Solution Overview
Version: Current build · Generated for review
1) What Payvance is
Payvance is a modern AP automation platform designed for invoice intake, OCR extraction, coding, approvals, audit history, and ERP export. It supports both QuickBooks Online and Microsoft Business Central integration paths.
Primary outcomes
- Faster invoice processing with standardized intake and OCR
- Controlled approvals with role-based workflow and traceability
- Cleaner accounting export with vendor/GL/terms validation
- Multi-tenant, domain-aware deployment for client rollouts
2) End-to-end process flow
Capture: invoices arrive by upload or email import.
Extract: OCR reads invoice fields (vendor, date, amount, etc.) and confidence.
Validate: AP maps vendor, GL account, terms, and supporting docs.
Approve: invoice moves through review and approval states with audit trail.
Export: approved invoices are pushed to the connected ERP.
Archive/Track: records remain searchable with status and metrics.
3) Integration architecture (pulling + pushing data)
3.1 Pulling data into Payvance
- Invoice source pull: Gmail-based import can pull invoice attachments into intake queues.
- Reference data pull: Payvance pulls ERP master data (vendors, GL/accounts, terms) via integration APIs.
- Lookup APIs: UI forms use live lookup endpoints so coding/approval uses current accounting references.
3.2 Pushing data out of Payvance
- Export gate: only approved invoices are eligible for export.
- Validation gate: vendor + GL + required fields are resolved before push.
- ERP bill creation: export endpoint creates bill transactions in the connected ERP.
- Post-export handling: invoice audit trail is updated and records can be auto-archived based on workflow rules.
4) QuickBooks integration path
- OAuth connection flow with redirect callback for tenant domain.
- Status endpoint verifies connection health/token state.
- Read operations pull vendors/accounts/terms for AP coding.
- Write operation pushes approved invoices as QuickBooks bills.
5) Business Central integration path
- OAuth connection flow with callback support and tenant base URL handling.
- Status endpoint provides integration state visibility.
- Reference data read path retrieves vendors and account mappings.
- Export path creates accounting records for approved AP documents.
6) Multi-tenant deployment model
Payvance includes an admin portal to provision and manage tenant instances. Each tenant can have dedicated hostnames, app base URLs, ERP redirect configuration, and runtime controls. This enables white-label deployments and clean separation across client environments.
7) Operational controls and governance
- Approval workflow and audit trail per invoice action.
- Role-based access and package-level feature controls.
- Health/log views and status observability in admin tooling.
- Domain-aware configuration to keep OAuth and public routing aligned.
Prepared by Arcubond for Payvance solution review.