E-Invoicing

Flowtly Editorial Team2 min

The E-Invoicing module in Flowtly enables organizations to send and receive electronic invoices in compliance with regulatory requirements. It integrates with the Polish National e-Invoice System (KSeF) to automate the exchange of structured invoice data between your organization and its counterparties.

Outbound invoices created in Flowtly can be automatically converted to the required XML format and submitted to KSeF. The module tracks submission status, stores confirmation numbers, and flags any validation errors so that issues can be resolved before they affect compliance deadlines.

Inbound invoice synchronization pulls invoices issued to your organization from KSeF directly into Flowtly. Received invoices are matched against existing supplier records and can be routed through approval workflows, reducing manual data entry and the risk of processing errors.

Invoice corrections are fully supported, including both corrective invoices and correction notes. The module maintains a clear audit trail linking original invoices to their corrections, ensuring that your records remain accurate and auditable at all times.

Example use cases

  • Submit outbound sales invoices to KSeF automatically upon approval in Flowtly.
  • Synchronize inbound purchase invoices from KSeF and route them for internal approval.
  • Generate and submit corrective invoices when billing errors are identified.
  • Monitor the status of all submitted invoices and resolve XML validation errors promptly.
  • Maintain a complete audit trail of all electronic invoice exchanges for regulatory compliance.

App routes

  • E-invoicing has no standalone route. Per-invoice actions open from a drawer at /clients/invoices/:id/e-invoicing; organization-wide e-invoicing configuration lives under Organization settings at /settings/organization/invoicing.

Connection map

Refers toUses upPart ofDerived from
Documented hereDocumented elsewhere
invoice billed to counterparty. invoice taxed by tax-group. cost spends against budget. cost owed to counterparty. bank-transaction reconciled to invoice. contract schedules payment-schedule-line. contract agreed with counterparty. contract attached to budget. budget covers project. invoice billed from project. project linked to budget. lead becomes counterparty. deal sold to counterparty.billed totaxed byspends againstowed toreconciled toschedulesagreed withattached tocoversbilled fromlinked tobecomessold toIInvoice — A sales document issued to a client: line items, dates, tax. It is created, reviewed, previewed and then sent.InvoiceCCounterparty — The other side of a financial document — a client billed, or a supplier owed.CounterpartyTTax group — The tax treatment applied to a line, so rates are set once rather than per document.Tax groupCCost — Money the organisation owes or has spent, tracked against a budget.CostBBudget — The financial envelope an engagement is measured against — what was planned, versus what has actually been spent.BudgetBBank transaction — A movement on a connected bank account. Matching it to an invoice or a cost is what makes the books agree with the bank.Bank transactionCContract — The financial terms of an engagement: a structured set of payment schedule lines, in one direction or the other.ContractPPayment schedule line — One dated amount on a contract, in a direction — money owed to a supplier, or due from a client.Payment schedule linePProject — The core organizational unit for a business initiative, client engagement or internal work. Everything tracked — time, cost, invoicing, profitability — hangs off one.ProjectPProspect — A company you are working but that is not a customer yet. It sits at New, Contacted or Qualified, and everything done to it is logged against it.ProspectDDeal — A sale in progress: a customer, an amount, and the stage it has reached. It cannot exist without a customer, and its stage is never blank.Deal

Related terms