Payment collection, dunning & portability — found from sitemap — Younium

Cited by

Facts read from this source

• Payments overview Report an error

  “Payments is the part of Younium that records money received from customers, matches those receipts to posted invoices, and updates invoice balances when payments are posted. It supports manual entry, structured bank file import, and CSV import, as well as payment collection through external providers documented separately.”

• Payment batches Report an error

  “A payment always belongs to a payment batch. Batches group related incoming transactions (for example one bank file or one manual session).”

• Partial batch posting Report an error

  “Batches can be partially posted: some payments in a batch may be posted while others remain open until they are fully matched and have no remaining amount.”

• Settlement writeoff types Report an error

  “Younium distinguishes two write-off types: Type Attached to Purpose Settlement (invoice) write-off A payment settlement Closes a small remaining balance on the matched invoice when within tolerance Payment write-off The payment itself Closes a small remaining amount on the payment after settlements when within tolerance”

• Payment currency exchange Report an error

  “When a payment in another currency is created without an amount in the base currency, Younium works it out from the payment's own exchange rate (or from the exchange rate for the payment date when no rate is given).”

• Provider ids on payment Report an error

  “Payments created by online collection providers can store provider identifiers on the payment record for reconciliation with external systems.”

• CSV import Report an error

  “Payments can be imported from CSV using a configurable field mapping. The import requires mapped fields for payment amount, currency code, and payment date. Imports can exclude negative amounts when configured.”

• CSV import templates Report an error

  “Import templates can be saved and reused as data import configurations for the payment entity.”

• Camt import Report an error

  “CAMT XML files (ISO 20022 bank-to-customer statement and debit/credit notification formats) are parsed into incoming payments. Supported schema variants include CAMT.053 (multiple versions) and CAMT.054.”

• Bgmax import Report an error

  “BGMAX files (Swedish bankgiro format) are parsed section by section. Only SEK currency sections are supported; other currencies are rejected.”

• Automatic matching Report an error

  “Automatic matching runs when batches are generated from imports or when a manual payment is created with reference search enabled. Only posted invoices are considered.”

• Reference extraction Report an error

  “The platform splits the payment reference on spaces, commas, periods, colons, and tabs, keeps numeric tokens, and trims leading zeros. Special handling applies to Danish OCR-style references beginning with IK71 0000.”

• Matching priority Report an error

  “1 OCR number Match token to invoice OCR reference (including structured OCR formats with + segments) 2 Invoice number Match token to invoice number (numeric comparison, leading zeros ignored) 3 Payer name and amount”

• Currency matching rule Report an error

  “A settlement is only created when the invoice currency matches the payment currency.”

• Duplicate detection Report an error

  “If an incoming payment carries an external bank id, the platform skips creating a payment when that id already exists on another payment. Empty external ids do not trigger duplicate detection.”

• Payment tolerance Report an error

  “Payment tolerance is optional. When configured, a positive tolerance amount and a tolerance financial account must both be set.”

• Tolerance default Report an error

  “Payment Tolerance Amount The largest remainder Younium will write off automatically, so a payment a few cents short still settles the invoice. Zero turns tolerance off 0”

• Posting effects Report an error

  “Posting finalises payments: it creates accounting transactions, sets the payment posted date, updates invoice status from settlements, and can update related sales order status for the batch.”

• Payment revert Report an error

  “A posted payment can be reverted when validation allows. Revert is blocked if accounting transactions for the payment are already on a posted journal.”

• Credit invoice balancing Report an error

  “When a posted credit invoice can be balanced against its debited invoice (debit invoice posted, no payments linked), the platform can create and post a balancing payment automatically using a selected method and account.”

• Payment methods per legal entity Report an error

  “Payment methods are configured per legal entity. Each method ties receipt posting to chart-of-accounts mappings.”

• Payment method fields Report an error

  “Financial Account The account payments received this way post to Exchange rate gains / Exchange rate losses Where exchange differences post when the payment is in another currency Bank fees Where a bank fee deducted from the payment posts”

• Payment term types Report an error

  “Net days The due date is the invoice date plus the number of days End of month, net days The due date is the end of the invoice month, plus the number of days Net days, end of month The due date is the number of days after the invoice date, then moved to the end of that month”

• Payment flows Report an error

  “Manual with reference search User creates payment Automatic on reference Manually created Manual without reference search User creates payment None at creation Manually created CAMT / BGMAX import User uploads bank file Automatic per section Bank file name CSV import User imports mapped file Automatic per currency section Import configuration Online provider Provider webhook / checkout (see payment integrations) Provider-specific; payment record stores provider ids Provider-driven”

• Payment providers Report an error

  “Payment provider integrations (Stripe, GoCardless, Aiia) handle collection and reconciliation with external systems; they are documented under Integrations → Payments.”

• Zero amount settlements Report an error

  “If the payment amount is exhausted but further reference tokens exist, the platform can still attach invoices with zero-amount settlements to reflect balancing scenarios (for example offsetting credit and debit invoices on one payment).”

• Manual settlements Report an error

  “Users can create settlements by linking one or more posted invoices to a payment. Settlement amounts are calculated from invoice balance and payment context.”

• Remaining amount formula Report an error

  “A payment’s remaining amount equals the payment amount minus the sum of settlement amounts minus the sum of payment-level write-offs.”

• Invoice status after posting Report an error

  “Zero Settled Set to latest settlement payment date Non-zero Posted (not settled) Payment date cleared”

Scores citing this record

• The Billing Engineer Payment collection, dunning & portability
• The Billing Engineer Invoices & e-invoicing compliance
• The Billing Engineer Payment collection, dunning & portability
• The Finance Lead Payment collection, dunning & portability
• The Finance Lead Payment collection, dunning & portability
• The SaaS Founder Payment collection, dunning & portability
• The SaaS Founder Payment collection, dunning & portability
• The Service-Business Owner Payment collection, dunning & portability
• The Service-Business Owner Payment collection, dunning & portability
• The Skeptic Payment collection, dunning & portability
• The Skeptic Payment collection, dunning & portability
• The Tax Adviser Payment collection, dunning & portability
• The Tax Adviser Payment collection, dunning & portability