Outbound invoices

Professional invoicing — legal clarity and repeatable workflows

A solid invoice anchors tax context, numbering discipline, traceability vs. delivery artefacts, and coherent references to approved time or project milestones—finance teams should not reconcile against guessing games.

Invoices module All capabilities

What a credible outbound invoice carries

Core elements—always tune with qualified tax advice:

Seller and buyer identification incl. postal details where invoicing rules require.
Strict sequential invoice numbering per numbering scheme without unexplained chronological gaps risking audit challenge.
Service date or service period articulated when materially relevant for VAT time of supply.
Net amounts and applicable tax rates per line when differentiated rates coexist.
Payment terms maturity bank references structured payment identifiers used by customers.
Explicit handling of reverse charge or small business exemptions when applicable—not implied footnotes.

Common mistakes draining time

Watch for these recurring issues:

Split numbering universes

Parallel ad-hoc series without central allocation invite duplicate or gap disputes.

Missing service windows

Unclear accrual timing complicates period cut-offs especially on long engagements.

Silent edits to finalised artefacts

Post-issuance rewriting conflicts with bookkeeping controls—document credit notes explicitly.

Isolated delivery effort

Invoices quoting hours disconnected from tracked project time crater under examiner spot checks.

Automated invoicing with cashwerk

Project/time context flows into guarded drafts avoiding manual archaeology.

Templates & field discipline

Validation and serial layouts minimise rejections from customers and accounting.

Status & collections

A/R states stay tethered—no orphaned shadow trackers.

Export readiness

Structured datasets for accountants and integrations—fewer unstructured rescans.

Keep GoBD expectations in sight

Invoices are prime audit samples: pair formal checks with change discipline after finalisation and archive exports that map back to project evidence.

Related product paths

Bind revenue to proof of performance.

Invoices deep dive →Quotes →Time tracking →Resources & glossary →

FAQ: Invoicing

Is PDF alone enough when partners require machine data?

Humans may need PDF, but growing B2B rails expect XML/ZUGFeRD/XRechnung—plan data once, render many outputs.

Automate recurring templates?

Yes when guardrails exist—auto series should still respect approvals for edge cases.

Reference projects cleanly?

Use structured object links instead of free text that later cannot tie to effort.

Foreign currency nuances?

Document conversion basis timestamp rounding policy—software should avoid manual spreadsheet rescues.

Partial then final invoices?

Model progressive billing without silent overlap—transparency beats hidden offsets.

Master data mistakes?

Keep VAT IDs and addresses fresh in CRM before invoice finalisation—no stale snapshot surprises.

Tighten invoicing operations?

Generate invoices from projects, timesheets, or quotes without parallel spreadsheet reconstructions.

Open invoices module

Laden...

What a credible outbound invoice carries

Core elements—always tune with qualified tax advice:

Seller and buyer identification incl. postal details where invoicing rules require.

Strict sequential invoice numbering per numbering scheme without unexplained chronological gaps risking audit challenge.

Service date or service period articulated when materially relevant for VAT time of supply.

Net amounts and applicable tax rates per line when differentiated rates coexist.

Payment terms maturity bank references structured payment identifiers used by customers.

Explicit handling of reverse charge or small business exemptions when applicable—not implied footnotes.

Common mistakes draining time

Watch for these recurring issues:

Split numbering universes

Parallel ad-hoc series without central allocation invite duplicate or gap disputes.

Missing service windows

Unclear accrual timing complicates period cut-offs especially on long engagements.

Silent edits to finalised artefacts

Post-issuance rewriting conflicts with bookkeeping controls—document credit notes explicitly.

Isolated delivery effort

Invoices quoting hours disconnected from tracked project time crater under examiner spot checks.

FAQ: Invoicing

Is PDF alone enough when partners require machine data?

Humans may need PDF, but growing B2B rails expect XML/ZUGFeRD/XRechnung—plan data once, render many outputs.

Automate recurring templates?

Yes when guardrails exist—auto series should still respect approvals for edge cases.

Reference projects cleanly?

Use structured object links instead of free text that later cannot tie to effort.

Foreign currency nuances?

Document conversion basis timestamp rounding policy—software should avoid manual spreadsheet rescues.

Partial then final invoices?

Model progressive billing without silent overlap—transparency beats hidden offsets.

Master data mistakes?

Keep VAT IDs and addresses fresh in CRM before invoice finalisation—no stale snapshot surprises.