# Documentation
Manage customers, segments, usage, health signals, and customer intelligence workflows.
Create quotes, structure contracts, manage subscriptions, and support hybrid pricing.
Track usage, sell prepaid credits, manage balances, and apply these patterns to AI monetization.
Generate invoices, manage taxes, documents, reminders, e-invoicing, and exports.
Connect payment providers, collect payments, retry failures, and reconcile transactions.
Track revenue, manage ledgers, automate journal entries, and handle revenue recognition.
Hyperline helps B2B software companies manage complex revenue workflows, from customer intelligence and CPQ to subscriptions, AI monetization, invoicing, payments, accounting, and developer integrations.
- Immediately: The date will be set to today, and result in a direct charge on your customer's payment method
- Checkout completion: It will create a checkout link for your customer to pay with. The issue date will match the payment date
As an alternative, you can [provide a free top-up on your customer's wallet](/docs/wallets/balance), which Hyperline uses to pay future invoices.
as tax exempt?"} A -- "Yes" --> B["VAT exempt"] A -- "No" --> C{"Is a manual VAT
rate set?"} C -- "Yes" --> D["Apply the manual VAT rate"] C -- "No" --> E{"Is the customer in
the EU VAT area?"} E -- "No" --> F["No EU VAT
Local tax rules may apply"] E -- "Yes" --> G{"Are the seller and customer
in the same VAT territory?"} G -- "Yes" --> H["Apply the seller-country VAT rate"] G -- "No" --> I{"Does the customer's VAT ID meet
your reverse-charge rules?"} I -- "Yes" --> J["Apply reverse charge
0% VAT"] I -- "No" --> K{"Is the customer typology
B2C (person)?"} K -- "No" --> H K -- "Yes" --> M{"Has this invoicing entity exceeded
€10,000 in eligible annual sales?"} M -- "No" --> H M -- "Yes" --> L["Apply the customer-country VAT rate"] classDef result fill:#FFF4D6,stroke:#E4B84B,color:#28251F; classDef exempt fill:#FCE8E6,stroke:#E39189,color:#28251F; class B,F exempt; class D,H,J,L result; ```
€350"] --> A1["Allocation
€200"] T --> A2["Allocation
€100"] T --> U["Unallocated
€50"] A1 --> I1["Invoice A"] A2 --> I2["Invoice B"] ``` ## Transactions, unallocated funds, and wallets An unallocated transaction and a wallet balance can both look like available customer funds, but they serve different purposes. | Concept | What it represents | How it is used | | - | - | - | | **Transaction** | A specific movement of money that has already happened or is being processed | Provides the source amount that can be assigned | | **Unallocated amount** | The part of a transaction that is not assigned to an invoice, credit note, or wallet | Waits for a manual matching decision | | **Wallet balance** | Funds intentionally made available on the customer's account | Can be used automatically or manually on future invoices | | **Wallet consumption** | A debit from the wallet used to pay an invoice | Reduces the wallet balance and contributes to the invoice payment | A transaction is evidence that money moved. It is not itself a customer balance. Its amount can be allocated directly to one or more invoices, added to the customer's wallet, or left unallocated while you decide how to match it. ```mermaid theme={null} flowchart LR T["Transaction received"] -->|"Allocate directly"| I["Invoice"] T -->|"Add to wallet"| W["Wallet balance"] W -->|"Use wallet funds"| I2["Current or future invoice"] T -->|"No decision yet"| U["Unallocated amount"] ```
€150"] -->|"€150"| C["Wallet consumption
€250"] F2["Second top-up
€200"] -->|"€100"| C F2 -->|"€100"| R["Remaining wallet funds"] ``` This history lets you identify which top-up funded each wallet consumption, including when one consumption uses several top-ups. If a wallet credit is reverted, Hyperline reallocates affected consumptions to other available funds where possible. Removing a direct transaction allocation and reversing a wallet payment are different operations: * **Unallocate** removes the relationship between a transaction and an invoice. The amount becomes unallocated on the same transaction. * **Reverse wallet payment** cancels the wallet consumption and returns the amount to the wallet balance. It does not create an unallocated transaction. Both operations recalculate the affected invoice, which can make a previously paid invoice payable again. See [Manage wallet balance](/docs/wallets/balance) for wallet top-up and consumption workflows. ## Accounting and reporting Current allocations are the source used to understand which documents a transaction settles. Hyperline uses them for invoice calculations, payment reporting, and supported accounting synchronization flows. Past allocation changes remain visible in the transaction's history for audit purposes but no longer affect current balances. Related refunds and chargebacks can still appear with the original invoice even when they have no current allocation. This keeps the full money-movement history understandable without counting an amount twice. ## How to read transaction relationships Use the following questions when investigating a payment: 1. **What money moved?** Review the payment, refund, or chargeback transaction. 2. **Where is it currently applied?** Review its current allocations and amounts. 3. **Was it applied somewhere else before?** Review the allocation changes in its history. 4. **Is it an adjustment?** Follow the link to its original payment. 5. **Did a credit note or wallet participate?** Review the related credit note applications or wallet funding sources.
