Invoicing & accounting software

Receipts enter the system by upload, mailbox or interface. Extracted values are checked against orders, contracts or timesheets; mismatches go to a clarification list. Outgoing invoices are generated from data that already exists — services, prices, payment terms — and are not typed again.

The result is an export for the tax adviser or the accounting system, for example in DATEV format. Incoming payments can be matched through the bank interface, so open items stay current without manual ticking off.

Three topics belong in the plan from the start. First, e-invoicing: companies must be able to receive structured invoices in domestic B2B trade, and the duty to send them is being phased in. The system should therefore read and produce XRechnung and ZUGFeRD.

Second, the GoBD rules: invoices must not be changeable after sending, corrections run through cancellation and reissue, and every change to master data is logged. Third, retention over the statutory periods. The tax assessment stays with your tax adviser — we implement their requirements technically.

Standard products are the better choice for standard processes. A custom solution pays off when billing arises from your core business and special rules apply there: usage-based pricing, commissions, billing by project progress, collective invoices across several entities.

Often the best answer is a mix: accounting stays in the proven product, and in front of it sits a lean application that models your special logic and hands over clean data. We settle the split in a short business analysis.

The interface is built quickly. The effort lies in the rules and in the edge cases that only show up when real month-end closings are played through.

• Pricing and tax logic: tiers, discounts, reverse charge, several currencies
• Number of connected systems: bank, DATEV, shop, time tracking, CRM
• Roles and approvals: who may issue, cancel and approve invoices
• Legacy data: migrating open items and customer master data cleanly