Distribution
Route leads to partners automatically with rules, caps, and invoicing.
Rules and their order
This is where you decide which partner receives which records. Every row is a rule: a partner, conditions, a price and limits. When a record comes in, the distribution walks the rules top to bottom and takes the first one that fits.
Read itWhat applies to the whole distribution
These settings apply to every partner of this record type: what is never distributed at all, how selection works, what a record costs, when a duplicate is a duplicate, whether returns are allowed, and the switch that halts delivery.
Read itThe partner list
A partner is whoever takes records. Here you keep who they are, where they are based and where the invoice goes: nothing more. How they are supplied and what they receive belongs to the distribution, because it differs per distribution.
Read itThe audit trail of a delivery
What happened to this one record at this one partner: the decision, every delivery attempt, the recipient's answer and, if it came to that, the return.
Read itAn invoice in detail
The lines of an invoice, its totals and its path: issued, sent, paid or corrected. Every line shows which delivery it comes from.
Read itThe portal as the partner sees it
A partner with access sees three pages: their records, their invoices and their settings. They see only what belongs to them, and only the fields released for partners in the record type.
Read itDistribution Analytics
Read the distribution analytics dashboard: delivered volume, revenue, cancellations, and per-partner performance over any time range.
Read itWhat actually went out
One row per partner and record: when, to whom, with what result and at what price. This list is the evidence, and at the same time the place where you see whether a connection works.
Read itA rule in detail
A rule window has four parts: conditions (who it matches), price (what the partner pays), limits (how much they receive at most) and delivery (where it goes). The last two apply to the partner within this distribution, not just to this one rule.
Read itAccess and portal rights
Here you decide who from a partner's organisation may enter the portal, and what that organisation may change there. Those are two different questions: the role applies to a person, the right to the whole partner.
Read itCreating and changing a partner
Contact details at the top, billing details below. The billing details decide whether an invoice may be created at all, and with which tax.
Read itDocuments and previews
One list with two kinds of rows: previews that still change, and invoices that carry a number and are therefore fixed. The number is the line between them.
Read itGoodwill requests
Once the return deadline has passed, a partner can no longer return a record themselves: they can only ask. Those requests sit above the delivery list, together with whatever they wrote.
Read itSender, rhythm and automation
What appears on every document, and when documents come into being. Without a complete sender the billing run issues nothing and says what is missing: an invoice without an address and a tax number is not one.
Read itThe dry run
The dry run takes a real record and works through the distribution without changing anything: no delivery, no price, no row in the list. It shows rule by rule what was decided and why.
Read itZUGFeRD and XRechnung
Two formats for the same thing: an invoice an accounting system can read. ZUGFeRD is a PDF with embedded data, XRechnung is the data on its own. Both are off by default.
Read it