Purchase before invoice
The requisition passes authority, budget, and approval checks. The purchase order becomes the reference point for the invoice and receipt.
An invoice arrives from KSeF (Poland's National e-Invoicing System) or by email, yet accounting still has to find the cost owner, purchase order, and correct approval path. We connect the entire process—from the document and purchase through the budget and ERP to payment preparation.
On the AMODIT platform, we design roles, rules, exceptions, and decision history. Integrations transfer data among KSeF, the workflow, an ERP or financial and accounting system, and the bank without creating another information silo.
The requisition passes authority, budget, and approval checks. The purchase order becomes the reference point for the invoice and receipt.
A missing purchase order, budget overrun, duplicate, or data discrepancy goes to the person responsible for the decision.
Finance and cost owners see the document stage, decision history, due dates, and data needed to analyze liabilities.
An invoice moves back and forth among accounting, the requester, and a manager because a purchase order or cost owner is missing.
The document is linked to the purchase order, budget, and approval rule, while any exception goes to the right person.
Invoice and purchase order
The CFO receives the forecast late because departments submit different spreadsheet versions.
The data has shared definitions, a schedule, and validation, and deviations are visible before publication.
Forecast and budget
A controller reconciles margin instead of analyzing the cause of a deviation.
An agreed model combines sales, discounts, costs, and source documents.
Margin and profitability
An analyst finds an error only after the report is published.
Data quality and lineage checks flag an incomplete data set before publication.
Data quality
An accountant receives a cost category without knowing why it was selected.
AI proposes a category or priority, and the accountant sees the input data and approves the selection.
AI under control
Requisitions, purchase orders, and budgeting form a separate solution area. It covers requisitions with authority-based approval, collecting proposals, supplier purchase orders, budget reservations and controls, and matching purchase orders with invoices and warehouse documents.
AI and OCR remain under user control. They read the document, propose data, and flag exceptions, while a person reviews and approves the output. We use existing models and configure them for the client's process—we do not train LLM or OCR models. We process AI data in a controlled environment in EU regions; the models are not trained on client data, which ensures compliance with the GDPR and the EU AI Act.
We adapt the process scope to the organization. The objective remains the same: connecting documents, people, and systems in one working environment.
This universal path shows the solution's scope. We configure roles, approval rules, and integrations for the company's environment.
The invoice enters the process regardless of channel and format.
OCR and AI propose data, and the user reviews the output.
AMODIT routes the document through roles, cost coding, and approvals.
Approved data and coding go to the financial system.
The process feeds payments, statuses, and cost and liability analytics.
AMODIT connects roles and the workflow, while KSeF Connector and integrations exchange documents, data, and statuses with the process environment.
Workflow, roles, rules, AI, and decision history.
We select the elements that fit the company's architecture. We use AMODIT and Astrafox products first, adding other vendors' solutions when the client's environment requires them.
On the Astrafox platform, we build invoice, purchasing, budgeting, and approval workflows with roles, due dates, notifications, and a decision trail.
See AMODIT →Astrafox's own product connects KSeF to any ERP or accounting system and handles communication, mapping, validation, statuses, and official acknowledgments (UPO) for companies operating in Poland.
See KSeF Connector →We capture headers and line items from invoices, bills, and receipts. KSeF documents use structured data, while other channels use OCR.
See AI solutions →We combine process and financial-system data in reports showing costs, liabilities, budgets, deadlines, and bottlenecks.
See Data & BI →We run the solution in the Astrafox cloud, the client's cloud, or the client's infrastructure, with defined access, backups, and maintenance accountability.
See Cloud & Infrastructure →We connect the workflow to SAP, Symfonia, Comarch ERP XL and Optima, enova365, TETA, Microsoft Dynamics, and other systems: master data, invoices, coding, and posting and payment statuses.
See Software & Integrations →Financial reporting supports root-cause analysis when measures share definitions, data passes quality controls, and users can move from a result to its source.
Revenue, costs, and results follow one methodology, and every value has a path to its source.
Plan, actuals, and deviations appear in the same period, company, and accountability context.
The team analyzes due dates, the receivables structure, and items that need attention without manually consolidating data.
It combines financial and sales metrics, presents the methodology, and prepares AI insights with access to source data.
See the product →It organizes report feeds, data testing, value lineage, and AI-assisted change publication.
See the product →We combine environment cost control, access separation, backups, and data recovery on Azure, Google Cloud, or AWS.
See Cloud & Infrastructure →Our projects have connected invoice and purchasing processes with SAP, Symfonia, Comarch ERP XL, Comarch ERP Optima, enova365, TETA, Microsoft Dynamics, and Exact. We also integrate other financial and ERP systems when they provide an interface required for secure exchange.
Depending on the process, the exchange covers master data, contractors, purchase orders, accounts and cost centers, invoices, coding, posting status, and payment status.
We do not limit the project to a basic invoice. We also organize related purchases, budgets, and payments.
Links to source documents and the appropriate handling path.
Separate master data, permissions, and rules for organizational units.
Controls for data, confidential B2B documents, and cases that require a decision.
Approval by role, amount, cost center, project, company, and purchase type.
Supplier proposals, purchase orders, and matching invoices to purchases and receipts.
Plan, use, fund reservations, and overrun alerts.
Accounts, cost centers, projects, and other dimensions sent to the financial system.
Polish and international payments, Elixir, and split payment.
This catalog combines repeatable and specialized project scopes: from documents and process rules to integrations, payments, and reporting. It presents the elements we select for each company's process and environment.
AMODITKSeF and KSeF 2.0AMODIT KSeF Connector and CloudAgent for on-premises systemsSAP ERP, SAP Business One, SAP Retail, and SAP PIOracle JD Edwards (JDE)Symfonia Finanse i Księgowość, Handel, and 50cloudComarch ERP XL, Optima, and Altumenova365TETAMicrosoft Dynamics 365, AX, Navision, and Business CentralExactStreamsoft VERTOWaproSubiekt nexo, Rewizor nexo, Navireo, and SferaKAMSOFT FKWInfor ERPRAKSRekordSIMPLE ERPSoftlabKsenofontProtel and Opera hotel systemstransportation and logistics systemsmedical and billing systemspurchasing and e-commerce systemscustom financial and operational systemsSharePoint and Power Appsskanuj.toAMODIT AI OCR and SmartOCRABBYY FineReader, Alphamoon OCR, and OCR in Microsoft AzureStatistics Poland (GUS), the Polish VAT whitelist, VIES, and National Bank of Poland exchange ratesbank integrations through APIs and filesmBank, Pekao, Santander, and BNP ParibasPolish and international banking formats, including Elixir batchesREST APIs, web services, and system connectorsstaging tables, SQL views, and stored procedures in MS SQL and MySQLODBCSFTP and FTPIDocXML and XSLTCSV, TXT, Excel, and XLSXPDF, DOCX, email, and network resourcesbarcodes and QR codesSSO, CAS SSO, Azure AD, KSeF tokens and certificates, SSL, and VPN tunnelsMicrosoft Azure, Debian Linux, and the client's on-premises infrastructure
purchase, cost, and incoming invoicessales invoicesadministrative, commission, and claims invoicesmaterials, warehouse, and goods invoicesinvestment, CAPEX, and project invoicesowner, internal, and commercial invoicesconfidential and restricted B2B invoicesPolish, international, and foreign-currency invoicesexpense invoices and utility, energy, and maintenance invoicestransportation, hotel, and manufacturing cost invoicescredit notes and correction notesaccrual notes, debit notes, and internal voucherspro forma invoices, advance invoices, and prepaymentscash and card-paid invoicesbills and receiptsaccounting, standard, and customs-and-tax documentsinvoices for reimbursement or paymenttickets and business trip documentspurchase requisitions and internal and supplier purchase orderssupplier proposals and related contractsgoods receipt (PZ), goods issue (WZ), and warehouse receipt documentsbudgets, forecasts, reservations, cost estimates, and cost planspayment batches and transfer filesstructured KSeF invoicesPDF scans, document images, and email attachmentssource and related documentsbank account data and SWIFT codescontractor and supplier master dataadvance and expense settlements
retrieving invoices from KSeFregistration from email, scan, network folder, or manual entrysplitting multiple invoices from one email or file packageclassifying documents into the correct workflowOCR or AI OCR reading with verification, correction, and re-readingbypassing OCR, XML mapping, and PDF visualization for KSeF invoicesduplicate, completeness, formal, arithmetic, and accounting compliance checksVAT, VIES, Statistics Poland, and Polish VAT whitelist verificationcreating contractor master data and verifying bank accountslinking corrections to source documentsconnecting invoice workflows with contracts and signaturescoding to accounts, cost centers, and projects and allocating costs among units and facilitiescoding templates and suggestions based on the contractor and historyapproval matrices based on amount, role, cost center, project, and purchase typesingle-level, multi-level, parallel, and conditional approval with substitutions and escalationreversal, return, and process error handlingseparate paths for companies and branches and B2B document confidentialityrequisitions, proposal collection, and supplier purchase order generationsupplier access to completion dates and commentsautomatic purchase orders from a budget or contractmatching invoices to requisitions, purchase orders, contracts, goods receipts, and goods issuessettling and comparing multiple invoices, purchase orders, receipts, and ERP dataimporting the plan and reserving, using, and restoring budgetsflagging overruns and adding approval for limitssending invoices and coding to ERP and receiving statusespayment status controlPolish and international transfer batches, including Elixirconsolidation, split payment, offsets, and scheduled paymentssending sales, retrieving purchases, and self-billing in KSeFonline and offline modes, retries, cancellation, statuses, and KSeF QR codesemergency XML retrieval and related-document searchesarchive, change history, retention, and document searchnotifications, follow-ups, and remindershandling documents in Polish, English, and other languages
document status, current stage, duration, and delaysapproval and change historypayment due datesposting and payment statusliabilities, planned payments, and documents awaiting transfercosts by account and cost centercosts by project, construction site, location, branch, facility, and vehicleplan, reservations, use, and available budgetbudget and limit overrunsunassigned invoices and documentsrequisitions and open and settled purchase orderslinks among purchase orders, invoices, and receiptssuppliers and bank accountserrors, duplicates, and missing dataKSeF statuses, errors, and confirmationsadvance, card, expense, reimbursement, and payment settlementsforecasts and cost provisionsmonthly and annual reportspivot reports, operational views, and management dashboardsExcel, CSV, and PDF exports
implementations in hundreds of organizationsprojects since 2011up to 60 companies in a single KSeF scopeup to 23,000 purchase documents per month in the largest scopeup to 1,700 production licenses in one organizationSaaS, client cloud, and on-premises installations
The scope ranges from single companies to multi-company groups and multi-branch organizations. Clients in this area include Rossmann, Neuca, Deutsche Bank, Weco-Travel, Netia, PCBC, Santander, Sportano, and Polmlek.









Grupa Żywiec
ResInvest Energy Chorzów
6 implementations of this type
We run the solution in the Astrafox cloud, the client's cloud, or the client's own infrastructure. The architecture follows the organization's security rules, integrations, and operational accountability.
We organize roles, documents, rules, exceptions, data sources, migration scope, and test scenarios.
We prepare environments, run user testing, and deliver training tailored to business and administration roles.
We provide maintenance, updates, error handling, user support, and process development following organizational and legal changes.
Invoices, purchase orders, budgets, receivables, and approval variants.
ERP, financial and accounting systems, banks, KSeF, CRM, data warehouses, files, and APIs.
Definitions, completeness, mapping, history, and validation rules.
The number of companies, locations, users, currencies, and charts of accounts.
Permissions, decision trail, retention, and acceptance scenarios.
Monitoring, error ownership, support, and further development.
These topics help distinguish the roles of KSeF, workflow, and ERP and prepare solution-selection criteria.
What actually shortens document processing and which stages should be organized before automation.
Read the article →How to distribute accountability among the national system, integration layer, workflow, and accounting.
Read the guide →Questions about processes, integrations, security, and maintenance to ask before purchasing a solution.
Read the guide →This page shows how we implement and integrate the solution in a company's environment. The AMODIT product website contains a detailed description of product functions.
Yes, when the system provides the interface required for the agreed exchange. We have connected processes with SAP, Symfonia, Comarch ERP XL and Optima, enova365, TETA, Microsoft Dynamics, and Exact. For another ERP, we first check the available APIs, services, tables, or file formats.
No. KSeF handles structured invoices and communication with the national system for companies operating in Poland. The company still needs cost-coding rules, substantive checks, accounting coding, approvals, exception handling, and data transfer for posting and payment.
Documents from email or scanners, and those added manually, pass through OCR or AI, data verification, and the same controlled path. The process distinguishes the document source without creating a separate workflow for every channel.
Yes. The scope connects the requisition, authority matrix, budget approval, proposals, purchase order, receipt, and invoice. The budget shows the plan, reservations, and use and flags overruns.
AI or OCR reads the document and proposes data, but a user verifies the output before it continues through the process. The system preserves the status, responsible person, and change history.
We first establish definitions for revenue, costs, periods, and exceptions. We then connect the required sources, build quality controls, and enable navigation from a result to its source data.
The process records the owner, status, decisions, comments, and change history, while the data layer records definitions, tests, runs, and publications.
The number of processes and exceptions, sources and integrations, data quality, organization scale, security requirements, history migration, and maintenance scope.
Yes. We run it in the Astrafox cloud, the client's cloud, or the client's infrastructure. The project defines data-processing locations, access, backups, integrations, and maintenance accountability. After launch, we provide SLA-based support, updates, and further development.
One team is accountable for the process, KSeF integration, connections to any ERP and banks, and solution maintenance. Product and implementation are covered by one point of accountability, including when an invoice passes through several systems.
Describe the document sources, ERP system, and step that requires the most manual work. We will organize the scope of the process, integrations, and accountability.
Describe your challenge