Collections Overview

when it comes to financial transactions and cash flow, “collections” typically refers to the process of collecting outstanding payments from customers effective collection processes are crucial for maintaining healthy cash flow and ensuring business sustainability this document provides an overview of how collections are approached within the nue ecosystem in nue, we ensure seamless integration with various payment systems such as stripe, quickbooks, netsuite, and others this integration allows users to leverage these systems for collection operations while ensuring that transaction data is properly written back to nue nue thus serves as a centralized transaction hub that monitors financial transactions and analyzes financial data in a unified way this document outlines the collection use cases applicable to most, if not all, integrations with payment systems these use cases are designed to ensure that regardless of the specific payment system used, the collection processes are efficient and the data integration is seamless this document serves as a guide for nue admin users and integration partners to understand the various collection use cases supported by nue and how to integrate a third party collection system with nue let's get started! primary concepts invoices, debit memos, and credit memos are considered billing transactions invoices request payment for goods or services provided, credit memos reduce the amount a customer owes typically due to returns or billing errors, and debit memos increase the amount a customer owes due to underbilling or additional charges the transactions are always represented at the item level, specifically invoice items debit memo items credit memo items each transaction contains the key transaction attributes, e,g transaction date, transaction amount, transaction currency, etc payments, refunds are considered payment transactions currently, nue does not own these transactions these are thus referred to as external transactions some systems represent transactions at the header level (e g stripe) because small medium businesses don't necessarily need that level of complexity some systems represent transactions at the line level (e g netsuite, zuora) nue manages all forms of billing transactions, and delegates to external systems for managing payment transactions additionally, nue records the relationship between payment transactions and billing transactions in the form of nue object model billing & usage accelerator docid\ bbq1oanzrrtmonpeuabak https //docs nue io/docs/developer resource/developer resource object model/object model billing accelerator/#payment application records payment application records can be of payment or refund record types the following diagram illustrates the above concepts collection operations collection operations typically involve a payment or a refund operation an external payment system typically also includes billing transactions, minimally invoices some systems also have some sort of credit memos or debit memos payment a payment operation creates a payment to an invoice or a debit memo when a customer makes a payment towards their outstanding balance, it reduces the a/r balance by the amount of the payment a payment can be collected via different payment methods it can also be paid from the credit balance of a customer refund a refund operation creates a refund to a payment credit memo in this approach, finance operations create a credit memo that is attached to the original invoice the credit memo serves as a record of the refund and is applied against the outstanding balance of the customer this method maintains a clear audit trail by linking the refund to the original transaction the credit memo can include details such as the reason for the refund, the refund amount, and any adjustments made to the customer's account invoice reversal alternatively, finance operations may choose to cancel the original invoice altogether instead of creating a credit memo, a new transaction is created to cancel out the original invoice this method effectively nullifies the original transaction, removing it from the accounts receivable balance however, it may be necessary to retain records of the cancellation and the associated refund for accounting and auditing purposes in the payment system, a refund can be issued back to the original payment, or issued as credits when a company issues a refund for a payment, the specific approach for handling it can vary depending on the company's policies and accounting practices however, there are two common methods to consider payment applications to streamline payment and refund processes external to nue systems, we use payment applications to document the payment and refund transactions related to invoices and credit memos within nue while payment applications do not constitute payment transactions on their own, they serve to record the connections between payments/refunds and invoices/credit memos it is important to know that in nue, an invoice may have multiple payment applications, and a payment application must only be associated with one invoice record types there are 4 record types for payment applications, each indicating a type of payment or refund operation record type description payment a payment type payment application is created when the invoice is paid via an external payment refund a refund type payment application is created when a paid invoice is refunded or canceled credit memo a credit memo type payment application is created when a credit memo is applied or unapplied to an invoice negative invoice a negative invoice type payment application is created when a negative invoice is applied or unapplied to an invoice operations there are the following operations available for the payment applications operation description pay this action occurs when paying an invoice, offsetting the invoice balance with a positive amount unpay this action is taken to reverse a payment on an invoice, resetting the invoice balance with a negative amount (this action will be available in future releases) refund this action involves refunding an invoice or canceling a paid invoice, associating a credit back credit memo with the invoice apply this action applies credit memos/negative invoices to an invoice, offsetting the invoice balance with a positive amount unapply this action reverses the application of credit memos/negative invoices to an invoice, resetting the invoice balance with a negative amount writeoff this action occurs when writing off an uncollectible invoice, associating a write off credit memo with the invoice (this action will be available in future releases) payment types there are the following payment types payment type description payment a payment type application occurs when a standard payment method is used to settle an invoice (e g credit card) credit memo a credit memo type application occurs when a credit memo is used to offset the balance of an invoice, for example, a credit memo in an external system is used to offset the balance of an invoice created in nue negative invoice a negative invoice type application occurs when a negative invoice is used to offset the balance of an invoice payment methods the following 2 payment methods are used for the operations payment method description electronic describes the process by which payments are handled through payment systems non electronic refers to the method by which payments are processed via cash or checks transaction amount and financial impact the transaction amount of a payment application record is always positive, unless the billing transaction is negative invoice that has a negative amount the combination of record type and operation fields determines the credit and debit impacts on financial accounts, as well as the signs used in financial reporting the following table helps in understanding the financial implications of various payment transactions, ensuring accurate record keeping and financial reporting record type operation description debit impact credit impact payment pay occurs when paying an invoice, decreasing the invoice balance increases cash/bank account (asset) decreases accounts receivable (asset) payment unpay (future) reverses a payment on an invoice, increasing the invoice balance decreases cash/bank account (asset) increases accounts receivable (asset) refund refund refunding or canceling a paid invoice, credit back memo applied increases accounts receivable (asset) decreases cash/bank account (asset) credit memo apply applies credit memos to an invoice, decreasing the invoice balance increases sales returns/allowances (contra) decreases accounts receivable (asset) credit memo unapply reverses applied credit memos, increasing the invoice balance decreases sales returns/allowances (contra) increases accounts receivable (asset) negative invoice apply applies negative invoices to an invoice, decreasing the invoice balance increases other revenue (revenue) decreases accounts receivable (asset) negative invoice unapply reverses applied negative invoices, increasing the invoice balance decreases other revenue (revenue) increases accounts receivable (asset) credit memo writeoff (future) writes off an uncollectible invoice, associating write off credit memo increases bad debt expense (expense) decreases accounts receivable (asset) billing transactions payment statuses explained the following payment statuses are used to indicate the payment status of billing transactions, including invoices, credit memos, and debit memos payment status description not transferred the billing transaction has not been transferred to the payment system transferred the billing transaction is transferred to the payment system successfully transfer error the billing transaction wasn’t successfully transferred to the payment system paid the billing transaction is paid in full (not applicable to credit memos) partially paid the billing transaction is partially paid (not applicable to credit memos) refunded the billing transaction is refunded (not applicable to credit memos) partially refunded the billing transaction is partially refunded (not applicable to credit memos) applied the billing transaction is applied (applicable to credit memos only) partially applied the billing transaction is partially applied (applicable to credit memos only) write off the billing transaction is written off (not applicable to credit memos) credit back the transaction is created as part of the refund process to offset invoices and debit memos canceled the billing transaction is canceled and has never been paid, then its payment status is set to canceled as well transaction hub in the complex landscape of finance and revenue operations, gaining a comprehensive understanding of billing transactions across various systems has been a challenge integrations with multiple external third party systems, spanning collection, accounting, taxation, and revenue recognition, adds layers of complexity it is critical to track the status of each transaction across these diverse platforms the transaction hub is a solution designed to provide granular visibility into the transfer status of every transaction across disparate external systems serving as a centralized control point, transaction hub empowers authorized users to seamlessly initiate and monitor the transfer of transaction records with ease and efficiency in nue, the mappings of all transactions and their mirror in the external systems are recorded in the transaction hub using the transaction hub, users can view the mapping information, the mirrored transactions’ statuses, and retry failed transaction mirroring upload a mapping between existing nue customers and customers in the payment systems users can upload a mapping between existing nue customers, and customers in the payment systems by following the steps below collect payments via stripe invoicing docid nbzb70twgpswffpy5hz quickbooks integration setup docid 6ry9nsmzdwog ci2judm1 upload a mapping between nue products and products in the payment systems users can upload a mapping between nue products and products in the payment systems by following the steps below quickbooks integration setup docid 6ry9nsmzdwog ci2judm1 view transaction status and payment status in nue users can view the transaction status and payment status of every billing transaction in nue through the transaction hub for supported integrations, including invoices, credit memos, and debit memos view mirrored transaction id users can view the mirrored transaction id through the transaction hub, as shown below retry failed transaction mirroring for each failed mirrorred billing transaction, users can manually retry the transfer of a single transaction in the transaction hub download transaction hub records users can use the export api https //api docs test nue io/#lifecycle manager export and import to export up to 10,000 transaction hub records into a csv file the following is a transaction hub export api example; curl location 'https //api nue io/api/cpq/async/exports' \\ \ header 'content type application/json' \\ \ header 'apiaccesskey;' \\ \ header 'nue api key {{nue api key}}' \\ \ data '{ "format" "csv", "objectnames" \["transactionhub"], "query" "query {transactionhub { id createdbyid createddate direction errorcode errormessage externalid externalsystem nueid status transactiontype} }" } ' then use the get export job result https //api docs test nue io/#get data export job status api to retrieve the exported csv file curl location 'https //api nue io/api/cpq/async/exports/{{export job id}}' \\ \ header 'apiaccesskey;' \\ \ header 'nue api key {{nue api key}}' collection scenarios in this section, we outline all the collection scenarios supported by nue, along with the webhooks and apis we provide for integration with third party payment systems it is important to note that some payment systems, such as stripe and quickbooks, support webhooks, while others may not therefore, the implementation of the payment scenarios may vary depending on the specific payment system used collections invoices docid q09xyhyqifwvezlfbcal collections credit memos and debit memos docid 0krorvd w29nwa95cfi13 collections payments docid\ rumboq75qhljedj09hz w collections refunds and reversals docid 6mgfqh1ccyvhdkz2mudr collections scenarios write off docid\ jtdowgvlnxgfypw0lhmvr