When documents, payments, and accounting operate separately
An accountant checks an invoice in email, the document workflow, and the ERP system before determining whether the document is complete and ready to be posted. The person responsible for payments manually matches bank transactions to receivables and payables. A controller combines one spreadsheet after another because operational and accounting reports use different data definitions.
After implementation, the document remains linked to its source, payment, and accounting entry. Rules handle repetitive tasks, while cases requiring judgment go to the right person. Finance and controlling work with agreed data instead of reconstructing the history across several systems.
Invoice and coding
Before: an accountant searches several places for the cost description, approval, and invoice coding data.
After: the approved data and document reach the correct accounting stage, while missing information triggers exception handling.
Bank statement and settlement
Before: an employee manually compares bank transactions with receivables and payables.
After: rules settle recurring cases, while ambiguous items remain for review.
Report and source of the result
Before: a controller reconciles figures from multiple spreadsheets before submitting a report to management.
After: the report uses agreed dimensions and lets the user trace a result back to the source data.
Complete finance implementation in Comarch ERP XL
We deliver complete finance and accounting implementations and provide ongoing support. We begin with how the team works: document sources, the chart of accounts, invoice coding rules, receivables and payables, payments, tax controls, user responsibilities, and reporting needs. We then configure the system, migrate the agreed data, prepare integrations and automation, conduct testing and training, launch the solution, and stabilize it.
Accounting and taxes
We configure the chart of accounts, journals, posting schemes, VAT registers, and rules for working with entries before and after approval. An operational document remains linked to its accounting entry, allowing the user to verify its source and current status.
Receivables, payables, and payments
We organize receivables, payables, due dates, offsets, and links between payments and documents. We develop rules for reminders, balance confirmations, and actions triggered by the status of a business partner’s account. We also automate the settlement of recurring bank-statement transactions, leaving ambiguous cases for review.
KSeF and invoice workflow
The project covers more than receiving or sending an invoice through KSeF (Poland’s National e-Invoicing System). We determine how the document is identified, described, approved, coded, and submitted for posting, as well as who handles missing data or exceptions. The integration layer and workflow are described in greater detail in the section on processes surrounding the ERP system.
Controlling and financial reporting
We agree on analytical dimensions, data sources, and responsibility for metric definitions. We develop reporting in XL or connect ERP data to a Business Intelligence solution when controlling needs a shared view across multiple companies, systems, or business areas.
Fixed assets
We connect fixed-asset implementation with accounting and responsibility for company assets. The scope covers records of tangible and intangible assets, inventory ledgers, documents, and depreciation. We implement and support this area as an integrated part of the XL finance environment.
Automation and extensions
We create rules and extensions for operations that should not be performed manually every time. Confirmed examples include automated bank-statement settlement, batch posting, invoice and report distribution, balance confirmations, and actions triggered by the current status of receivables and payables.
From analysis to launch and stabilization
- Process and data analysis. We establish the documents, roles, chart of accounts, posting rules, receivables and payables, payments, reports, migration data, and connected systems.
- Solution design. We define the XL configuration, integrations, automation, extensions, and exception-handling scenarios.
- Configuration and migration. We prepare the environment, configure the agreed scope, and migrate validated data.
- Integrations and testing. We connect XL to banks, KSeF, document workflows, and reporting. We test complete scenarios from the source document through posting and reporting.
- Training and launch. We prepare users, launch the solution, and stabilize the process after go-live.
- Support and development. We maintain the finance module, integrations, and extensions, and develop them as the company changes.
See the full scope of a Comarch ERP XL implementation →
Comarch ERP XL in a company-wide process
The ERP system stores finance and accounting data, but a document’s path often starts earlier, and a management report combines more than one source. We design responsibilities and data exchange between XL and the processes around it so users can see a case’s status without re-entering the same information.
AI under user control
AI and OCR read a document, suggest data or a category, and flag exceptions. A person reviews and approves the result before the information moves to the next process or the ERP system.
See AI solutions →AMODIT for workflow and approvals
AMODIT guides an invoice, purchase, or other document through description, invoice coding, approval, and exception handling. The integration sends approved data to XL and receives the posting or payment status.
See invoice and purchasing workflows →KSeF Connector
Astrafox's own component connects KSeF with Comarch ERP XL, document workflows, and other systems used across the group. It handles mapping, validation, statuses, official receipt acknowledgments, and exchange monitoring.
See KSeF Connector →BI for finance and controlling
We combine XL data with sales, operational, and external information. Reports show costs, receivables, payables, budgets, and results based on shared definitions.
See Data & BI solutions →Functions available directly in the vendor’s environment are described separately under KSeF in Comarch ERP XL. When a process needs to cover KSeF, approvals, different ERP systems, and reporting, the starting point is KSeF Connector, AMODIT, and Astrafox integrations.
Maintenance and SLA after launch
After go-live, we take responsibility for the finance module, its configuration, integrations, automation, and reports. Every ticket has an owner, priority, and next step. Under an SLA, we define ticket categories, response times, availability, contact channels, and responsibilities.
We also take over existing environments. We begin by diagnosing the configuration, data quality, customizations, integrations, reports, and documentation. We then organize ticket handling, resolve problems, and plan further development without replacing components that work correctly.
See maintenance and SLA for Comarch ERP XL →
Frequently asked questions about finance in Comarch ERP XL
What does finance and accounting in Comarch ERP XL cover?
It covers general ledger accounting, the chart of accounts, journals, posting schemes, VAT registers, receivables and payables, cash and bank transactions, financial reporting, and links between operational documents and accounting entries. The project scope follows the processes, organizational structure, and reporting needs.
Does Astrafox implement the full finance scope in Comarch ERP XL?
Yes. We provide complete implementation and support for this area: from analysis, configuration, and data migration through integrations, testing, and user preparation to go-live, stabilization, and further development.
How do you connect Comarch ERP XL to KSeF and an invoice workflow?
KSeF Connector handles document exchange, mapping, validation, statuses, and official receipt acknowledgments. AMODIT manages description, invoice coding, approvals, and exceptions, while the integration sends approved data to XL and receives posting and payment information.
Does the implementation include fixed assets?
Yes. We implement and support records of tangible and intangible assets, inventory ledgers, documents, and depreciation, connecting this scope with accounting and responsibility for company assets.
How do you connect Comarch ERP XL data with controlling and BI?
First, we agree on measure definitions, analytical dimensions, and data sources. We then develop reports in XL or feed ERP and other system data into a BI solution so controlling has a shared view of costs, receivables and payables, budgets, and results.
Can the finance module be covered by an SLA?
Yes. SLA support covers Comarch ERP XL, the finance module configuration, integrations, extensions, and reports. The agreement defines ticket categories, response times, availability, contact channels, and service responsibilities.