Governed Invoice, Receipt, Tax, and Financial Record Management — with AP/AR Automation, Audit-Ready Retention, and Cost-Optimised Archives on AWS
Accounting and finance departments produce and receive more governed documents than almost any other function in the organisation. Invoices, receipts, purchase orders, bank statements, tax filings, journal entry support, expense reports, financial statements, audit workpapers, and regulatory filings — all of these must be captured, classified, approved, retained for specific periods, and producible on demand for auditors, tax authorities, and regulators.
Yet in most organisations, financial documents are scattered across accounting software attachments, email inboxes, shared drives, expense management tools, and paper files. Invoice processing is manual — download from email, enter into the accounting system, route a PDF for approval, file somewhere that someone might find it later. Tax records are retained in filing cabinets or unmanaged folders with no defensible evidence that retention requirements were met. And when auditors arrive — whether internal, external, or regulatory — the finance team spends days assembling documentation from multiple sources.
FormKiQ provides governed document management and archival storage specifically for accounting and financial content — deployed directly into your AWS account, with AP/AR document workflows, tax-aware retention policies, audit-ready evidence production, and integration with accounting and ERP systems through the ERP Integration Framework.
The Accounting Document Problem
Accounting systems are designed to manage transactions, not documents. The invoices, receipts, and supporting documentation that evidence those transactions are treated as attachments — uploaded to the accounting system with no independent governance, no document-level search, and no retention enforcement separate from the transaction record.
| Challenge | What Goes Wrong | FormKiQ Resolution |
|---|---|---|
| Documents as attachments | Financial documents attached to accounting records with no independent classification, search, or lifecycle | Documents stored as governed records with structured metadata, full-text search, and independent lifecycle management |
| Manual invoice processing | Invoices arrive by email, are manually downloaded, manually entered, manually routed for approval | Email Ingestion Gateway captures invoices automatically; IDP extracts data; workflows route for approval |
| No document-level retention | Retention tied to the accounting record — if the transaction is purged, supporting documents may be lost | Configurable retention by document type, tax jurisdiction, and regulatory requirement — independent of accounting system lifecycle |
| Audit evidence gaps | No audit trail for document access; no defensible evidence of retention compliance | Every document access, approval, and disposition event logged with timestamps and actor identification |
| Storage cost | Financial documents stored in accounting system database at premium rates — or in unmanaged shared drives at zero governance | Documents stored in Amazon S3 with tiered storage — active through archival — at a fraction of accounting system storage cost |
| Multi-jurisdiction tax retention | Different tax jurisdictions require different retention periods for the same document types — managed manually or not at all | Jurisdiction-aware retention policies with configurable periods by document type and tax jurisdiction |
| Audit preparation | Weeks of document assembly before each audit cycle | Audit-ready evidence produced continuously; documents searchable and producible on demand |
Financial Document Types and Governance
Accounts Payable
| Document Type | Active Management | Archive / Retention Use Case |
|---|---|---|
| Vendor invoices | IDP extraction, three-way matching, AP approval workflows, payment authorisation | Tax audit support, vendor dispute resolution, SOX evidence |
| Credit notes | Matching to original invoice, approval workflow, accounting adjustment | Financial reconciliation reference, audit evidence |
| Purchase orders | PO creation, approval workflows, matching to invoices and receipts | Procurement audit trail, vendor relationship history |
| Goods receipts / delivery confirmations | Receipt matching, quality verification, three-way match documentation | Proof of delivery, warranty claims, dispute evidence |
| Expense reports and receipts | Submission workflows, manager approval, policy compliance verification | Tax deductibility evidence, policy compliance audit |
Accounts Receivable
| Document Type | Active Management | Archive / Retention Use Case |
|---|---|---|
| Customer invoices | Invoice generation, delivery tracking, payment matching | Revenue recognition evidence, tax audit, accounts ageing reference |
| Customer contracts and agreements | Contract lifecycle management, billing schedule tracking, renewal alerting | Revenue recognition, customer dispute resolution, regulatory retention |
| Credit applications | Application intake, credit assessment workflows, approval documentation | Credit decision audit trail, regulatory evidence |
| Collection correspondence | Correspondence tracking, escalation workflows, settlement documentation | Legal reference, regulatory compliance, dispute history |
Tax and Regulatory
| Document Type | Active Management | Archive / Retention Use Case |
|---|---|---|
| Tax returns and filings | Preparation workflows, review and approval, filing confirmation tracking | Statutory retention (typically 4–10 years depending on jurisdiction), audit defence |
| GST/HST/VAT returns | Preparation, review, filing, refund tracking | Statutory retention, tax authority audit |
| Transfer pricing documentation | Preparation, intercompany agreement management, regulatory filing | Statutory retention, cross-border tax audit defence |
| Regulatory filings | Preparation workflows, approval, submission tracking, confirmation documentation | Regulatory retention, examination readiness |
Financial Reporting and Audit
| Document Type | Active Management | Archive / Retention Use Case |
|---|---|---|
| Financial statements | Preparation, review, approval, distribution controls | Statutory retention, investor relations, audit reference |
| Journal entry support | Supporting documentation linked to journal entries, approval workflows | SOX compliance evidence, internal and external audit |
| Bank statements and reconciliations | Receipt, reconciliation workflows, discrepancy resolution | Audit evidence, regulatory retention, fraud investigation reference |
| Audit workpapers | Internal and external audit documentation, finding tracking, management responses | Audit history, regulatory examination, SOX compliance |
Invoice Processing Automation
Invoice processing is the highest-volume, most-automatable financial document workflow. FormKiQ's IDP pipeline eliminates the manual steps.
How Automated Invoice Processing Works
| Step | What Happens | Manual Equivalent Eliminated |
|---|---|---|
| Capture | Invoices arrive via email, SFTP, scanner, or API — captured by Document Gateway Modules | Downloading email attachments, scanning paper invoices |
| OCR / Textract extraction | Vendor name, invoice number, date, line items, tax amounts, and total extracted as structured data | Manual data entry into accounting system |
| Metadata mapping | Extracted fields mapped to FormKiQ metadata and cross-referenced with vendor and PO records | Manual lookup and cross-referencing |
| Duplicate detection | Invoice number and vendor checked against existing records to flag potential duplicates | Manual spreadsheet checking |
| Three-way match | Invoice data compared against PO and goods receipt data — matches advance automatically, exceptions flagged | Manual comparison of three paper documents |
| Approval routing | Invoices routed through configurable approval workflows based on amount, vendor, cost centre, department, or exception type | Email chains asking "can you approve this?" |
| Accounting system sync | Approved invoices and extracted data synchronised to the accounting or ERP system for payment | Manual re-entry into accounting software |
| Governed storage | Processed invoices retained in FormKiQ with full metadata, audit trail, and tiered archival storage | Filing in a shared drive or filing cabinet |
AI-Enhanced Invoice Processing
FormKiQ's AI Processing and Analysis module — powered by Amazon Bedrock — adds intelligence beyond what Textract extraction provides. All AI processing runs within your AWS account; financial document content never leaves your cloud environment.
| AI Capability | Invoice Application |
|---|---|
| Vendor classification | Automatically classify invoices by vendor category (utilities, professional services, materials, software) for cost analysis and approval routing |
| Anomaly detection | Flag invoices with unusual amounts, unusual vendors, or patterns that deviate from historical norms — supporting fraud prevention |
| Policy compliance | Assess invoices against procurement policy requirements — flagging invoices that exceed policy thresholds or bypass required procurement processes |
| Tax classification | Identify applicable tax treatment based on invoice content, vendor jurisdiction, and transaction type |
Tax-Aware Retention
Financial document retention is driven by tax law, corporate law, and regulatory requirements — and the requirements vary significantly by jurisdiction. FormKiQ supports multi-jurisdiction tax retention with configurable periods per document type and tax authority:
| Jurisdiction | Document Category | Typical Retention | Regulatory Driver |
|---|---|---|---|
| Canada (Federal) | Income tax records | 6 years from end of tax year | Income Tax Act |
| Canada (GST/HST) | GST/HST records | 6 years from end of tax year | Excise Tax Act |
| United Kingdom | Company tax records | 6 years from end of accounting period | Companies Act 2006, HMRC |
| United Kingdom | VAT records | 6 years | VAT Regulations 1995 |
| European Union | VAT records | 5–10 years (varies by member state) | EU VAT Directive, national implementation |
| Australia | Tax records | 5 years from date of filing | Taxation Administration Act 1953 |
| United States | Federal tax records | 3–7 years depending on circumstance | Internal Revenue Code |
| United States (SOX) | Audit-related financial records | 7 years | Sarbanes-Oxley Act |
| New Zealand | Tax records | 7 years | Tax Administration Act 1994 |
| Singapore | Business records and tax documents | 5 years from relevant year of assessment | Income Tax Act, IRAS requirements |
| India | Income tax records | 6 years from end of relevant assessment year | Income Tax Act 1961 |
Audit Readiness for Financial Documents
Financial audits — internal, external, and regulatory — are the primary use case for financial document governance. FormKiQ produces audit evidence continuously rather than requiring assembly before each audit cycle.
| Audit Evidence | What's Required | Where It Lives in FormKiQ |
|---|---|---|
| Transaction support | Supporting documentation for every material transaction — invoices, POs, receipts, contracts, approvals | Documents stored with metadata linking them to transactions; searchable by transaction reference, vendor, amount, date |
| Approval evidence | Proof that transactions were authorised by appropriate personnel | Workflow approval decisions audit-logged with approver identity, timestamp, and approval chain |
| Segregation of duties | Evidence that incompatible duties are separated — no single person can initiate, approve, and record a transaction | ABAC access policies enforcing role separation; workflow configuration preventing self-approval |
| Retention compliance | Evidence that financial records are retained for required periods | Retention policies documented; retention enforcement automated; disposition audit-logged |
| Access controls | Evidence of who can access financial documents and how access is authorised | ABAC policies documented; access audit trail showing all document access events |
Archival Storage for Financial Documents
Financial document archives are among the longest-lived in any organisation — tax records commonly retained for 6–10 years, SOX-related records for 7 years, and some corporate records permanently. FormKiQ provides cost-optimised archival using Amazon S3:
| Retention Phase | S3 Tier | Cost Advantage | Use Case |
|---|---|---|---|
| Current fiscal year | S3 Standard | Significantly lower than accounting software storage | Active invoices, current-period documents |
| Prior fiscal year | S3 Infrequent Access | ~45% lower than S3 Standard | Recently completed period — referenced during year-end close and audit |
| 2–5 years | S3 Glacier Instant Retrieval | ~68% lower than S3 Standard | Tax audit window — immediate access when needed |
| 5–10 years | S3 Glacier Flexible Retrieval | ~78% lower than S3 Standard | Extended statutory retention — retrievable within hours |
| 10+ years / permanent | S3 Glacier Deep Archive | ~95% lower than S3 Standard | Long-term statutory retention, permanent corporate records |
Documents transition between tiers automatically without losing metadata, search indexes, or audit trails. A seven-year-old tax document archived to Glacier is still searchable by vendor, amount, tax year, and jurisdiction.
Compliance and Regulatory Alignment
| Framework | Financial Document Requirements | FormKiQ Capabilities |
|---|---|---|
| SOX (Sarbanes-Oxley) | Financial record retention, internal controls over financial reporting, audit trail for approvals | Approval workflows with audit trails, retention enforcement, segregation of duties enforcement, supporting document linkage |
| IFRS / national GAAP | Supporting documentation for financial statement assertions | Document-to-transaction linkage, retention, searchability, audit evidence production |
| National tax legislation | Tax record retention for statutory periods varying by jurisdiction | Jurisdiction-aware retention with configurable periods by document type and tax authority |
| VAT / GST / HST | Transaction records, tax invoices, and returns retained for statutory periods | Retention enforcement, document classification by tax type, cross-border tax documentation |
| Anti-money laundering | Transaction documentation, customer due diligence records, suspicious activity reporting | Document classification, retention enforcement, access controls, audit trails |
| GDPR / Privacy legislation | Personal data in financial documents subject to data protection requirements | Sensitivity classification, access controls, retention limits, data residency enforcement |
| SOC 2 | Access controls, audit logging, and operational monitoring for financial data handling | Audit logging, access controls, encryption, operational monitoring |
Who Uses Accounting and Financial Document Management on AWS
| Industry | Financial Document Challenges | Key Drivers |
|---|---|---|
| Financial services | High-volume transaction documentation, multi-jurisdiction regulatory filings, client financial records | SOX, national financial regulation, audit examination readiness |
| Manufacturing | Procurement documentation, cost accounting records, multi-facility financial consolidation | SOX (if public), tax compliance across jurisdictions, supply chain financial documentation |
| Healthcare | Insurance billing documentation, patient financial records, grant financial reporting | Healthcare financial regulation, grant compliance (2 CFR 200), insurance audit |
| Government and public sector | Public fund accountability, grant financial administration, procurement documentation | Public audit requirements, grant financial compliance, transparency mandates |
| Technology and SaaS | Revenue recognition documentation, subscription billing records, multi-jurisdiction tax compliance | ASC 606 / IFRS 15, SOX (if public), multi-jurisdiction tax retention |
| Nonprofits | Donor financial records, grant expenditure documentation, programme cost allocation, audit evidence | Funder financial reporting, charity regulator requirements, annual audit |
FormKiQ Editions for Accounting and Financial Document Management
| Capability | Core | Essentials | Advanced | Enterprise |
|---|---|---|---|---|
| Document Storage (S3) & API | ✓ | ✓ | ✓ | ✓ |
| Tagging, Search & Classification | ✓ | ✓ | ✓ | ✓ |
| OCR (Tesseract) | ✓ | ✓ | ✓ | ✓ |
| OCR & IDP (Textract) | ✓ | ✓ | ✓ | |
| SSO (SAML — Entra, Google, Auth0) | ✓ | ✓ | ✓ | |
| Workflows, Queues & Rulesets | ✓ | ✓ | ✓ | |
| Encryption (KMS — in-transit & at-rest) | ✓ | ✓ | ✓ | |
| Document Control & Versioning | ✓ | ✓ | ✓ | |
| Antivirus & Anti-Malware | ✓ | ✓ | ✓ | |
| ERP / Accounting Integration Framework | ✓ | ✓ | ||
| AI Processing & Analysis (Bedrock) | ✓ | ✓ | ||
| Document Generation | ✓ | ✓ | ||
| eSignature Integration | ✓ | ✓ | ||
| Email Ingestion Gateway | ✓ | ✓ | ||
| Enhanced Full-Text Search (OpenSearch) | ✓ | ✓ | ||
| Multi-Instance & Multi-Region Licensing | ✓ | ✓ | ||
| Vendor-Managed & Hybrid Deployment | ✓ | |||
| Custom SLAs & Compliance Consulting | ✓ | |||
| Support | Community (Slack & GitHub) | Support Portal (2-business-day SLA) | Private Slack + videoconference + 40 hrs onboarding | Rapid response (8-business-hour SLA) + strategic architecture support |
Deployment Models
| Model | Description | Availability |
|---|---|---|
| Customer-Managed AWS | Deploys directly into your AWS account via CloudFormation. Full control of infrastructure, networking, encryption keys, and operations. | All editions |
| Vendor-Managed | FormKiQ manages the AWS infrastructure on your behalf — deployment, updates, and operational support. | Enterprise |
| Hybrid | You retain control of specific components (encryption keys, network config) while delegating operational management to FormKiQ. | Enterprise |
Every deployment is a dedicated, isolated instance. FormKiQ does not operate a shared multi-tenant environment.
Getting Started
FormKiQ Core can be deployed to your AWS account in fifteen to twenty minutes. Accounting and financial document management capabilities — including ERP Integration Framework, AI-powered invoice processing, Email Ingestion Gateway, and tax-aware retention — are available on FormKiQ Advanced and Enterprise.
Frequently Asked Questions
Why not just store financial documents in our accounting software?
Accounting software treats documents as attachments to transactions. It doesn't provide independent classification, full-text search across document content, document-level retention policies, legal hold, segregation of duties enforcement for document access, or cost-optimised archival storage for the years or decades that financial records must be retained. FormKiQ provides all of these capabilities while maintaining the link between accounting transactions and their supporting documents.
How does automated invoice processing work?
Invoices arrive via email, SFTP, scanner, or API and are captured automatically. Amazon Textract extracts vendor, amount, line items, and other structured data. Custom mappings apply extracted data as searchable metadata and cross-reference against vendor and PO records. Three-way matching compares invoice data against PO and receipt data. Approved invoices are synchronised to your accounting system. The entire process is audit-logged.
How does FormKiQ handle tax retention across multiple jurisdictions?
FormKiQ supports configurable retention policies by document type and tax jurisdiction. Canadian federal tax records can follow a 6-year retention from fiscal year end while UK VAT records follow 6 years from the VAT return period — both within the same deployment. The retention clock can be configured to start from filing date, fiscal year end, or other reference point as required by the applicable tax authority.
Can auditors access financial documents directly in FormKiQ?
Yes. FormKiQ's access control model supports time-limited, read-only auditor access scoped to specific document categories and audit periods. All auditor access events are recorded in the audit trail. Documents can be produced by searching on any combination of metadata — vendor, amount, date range, document type, cost centre — and exported for auditor review.
How does FormKiQ support SOX compliance?
FormKiQ supports SOX-relevant controls through approval workflows with audit trails (evidencing authorised transactions), ABAC access policies (enforcing segregation of duties), document versioning (protecting integrity of financial records), retention enforcement (7-year retention for audit-related records), and continuous audit evidence production (access logs, approval records, retention evidence).
What happens to financial documents when we change accounting systems?
Documents managed in FormKiQ are independent of the accounting platform. When you migrate to a new accounting system, your financial documents, metadata, retention policies, access controls, and audit trails all persist — only the integration layer needs to be reconfigured. This eliminates document migration risk during accounting system transitions and ensures retention continuity across platform changes.