KSeF for small companies: how to prepare

The move to e-invoices via KSeF is feasible for small firms if done step by step. Below are minimum requirements and a practical plan.

Minimum requirements

• An accounting/ERP system that can generate e-invoice structures and integrate with the KSeF API or a connector.
• Configured roles and permissions: creation, signature, submission, correction.
• Clean master data: unified names, NIP numbers, addresses, payment methods.
• Basic policies for storage, archiving and logging.

Implementation steps

1. Assess the current invoicing process and identify manual points.
2. Choose integration: native ERP module or external connector.
3. Set numbering rules, description templates and VAT mappings.
4. Run a pilot on a small set of customers/orders.
5. Test scenarios: base e-invoice, advances, corrections, returns.
6. Update instructions and train the team; move to BAU.

Automate first

• Create e-invoices directly from orders or delivery/acceptance notes.
• Automatic submission to KSeF and status tracking.
• Payment reminders and reconciliation.

Common pitfalls

• Duplicate counterparties and inconsistent details.
• Mixed numbering rules across departments.
• No operation log or clear ownership.

Budget and scope

• Minimum: KSeF connector, basic validation, archive.
• Optional: role model, bulk operations, management reports.

An early pilot reduces go-live risk once KSeF becomes mandatory.