The Nue Billing & Collections server exposes Nue's Everything Billing and collections capabilities as MCP tools. It covers the stage of the revenue lifecycle that begins once an order is activated: issuing billing transactions, recording their settlement, and maintaining an accurate view of accounts receivable across every system that holds a copy of them.

Nue draws a deliberate distinction between two classes of transaction, and that distinction shapes the tool set. Billing transactions — invoices, credit memos, and debit memos — are owned by Nue and managed end to end through this server. Payment transactions — payments and refunds — are executed in the payment system of record, whether that is Stripe, QuickBooks, NetSuite, or another provider. Nue records their relationship to the underlying billing transactions as payment applications, so the effect of every settlement, application, reversal, and write-off on the receivable balance remains auditable from within Nue. The server also exposes the synchronization operations behind the Transaction Hub, through which finance teams confirm that each transaction has reached its downstream systems intact and retry those that have not.

Collections is, in the end, the discipline of converting issued invoices into received cash, and it is material to the health of the business rather than a matter of administrative tidiness. The work is periodic, high in volume, and unforgiving of small errors, since an error on an invoice is one the customer sees. A substantial share of the effort is not judgement but assembly: identifying the transactions that match a given description, applying the correct credit to the correct document, pursuing balances that remain outstanding, and confirming that each record has reached the accounting and CRM systems that depend on it. That assembly work is what an assistant connected to this server is well suited to undertake, with the commercial and accounting decisions remaining with your finance and billing operators.

A billing manager can ask for every overdue invoice on a named account and have the balances summarised. A collections specialist can apply an existing credit memo to the invoices it should offset, and see immediately what remains outstanding. An operations lead can set up a recurring billing schedule described in ordinary language — the first Monday of each month, say — without translating that into a scheduling expression by hand. Each of these is a request that would otherwise mean several screens and a good deal of care.

This is the broadest of Nue's MCP servers. The breadth reflects the reality of billing, where the same document may need to be created, corrected, activated, cancelled, synchronised, and reported on, and where each of those steps is a distinct operation with its own rules.

Because the set is large, the gateway's tool search does meaningful work here: an assistant finds the handful of tools relevant to your request rather than reasoning over the whole surface at once. Tools appear under the billing_ prefix.

The sections below group the tools the way a billing team thinks about its own work.

Invoices are the centre of the server. These tools cover a document's whole life, from correction and activation through to cancellation, along with the operations that keep invoice records aligned with connected systems. Activation is the step that makes an invoice real and visible to the customer, and several operations exist in both an immediate and a background form so that large runs do not have to be processed one document at a time.

Credit memos record amounts owed back to a customer, whether from an overcharge, a cancellation, a negotiated concession, or the conversion of unused credit. They follow the same shape as invoices — created, amended, activated, and sometimes cancelled — and they carry the additional question of what they have been applied to.

Debit memos record additional amounts a customer owes beyond what has already been invoiced, and are the natural counterpart to credit memos.

Payment rules describe how and when payment should be taken. Setting them up well is what turns collection from a manual chase into something that largely runs itself, and these tools cover their whole life, including the ability to copy an existing rule as the starting point for a new one.

A billing schedule determines when billing runs happen and which customers and products they cover. Describing a schedule in ordinary language — the first Monday of the month at two in the morning — is exactly the kind of translation an assistant handles well, and the server accepts the resulting definition directly.

These two read-only tools answer the questions a billing operator asks the morning after a run: what ran, what is still processing, what failed, and why. Neither writes anything, so neither asks for confirmation.

getBillingActivity answers for the whole tenant, so it is refused in a conversation confined to one customer. getBillingJobResults reads any job under All Accounts; in one customer's conversation it reads only a job that billed that customer alone, which is what "is it done?" needs after a run started there. Reasons come only from the job's error log or the job's own message, never from inference. In an MCP App host, the job's card offers Download CSV, a signed link to the complete error log that is valid for 15 minutes; the link is passed to the card only and never appears in the text a model reads.

Collections is the work of turning issued invoices into received money, and of resolving the cases where that does not happen cleanly. These are the most consequential tools on the server, because each one moves money or forgives it.

For tenants running Nue on Salesforce, billing documents need to appear in the CRM as well. These tools drive that synchronisation and let an assistant confirm it has completed, which matters when a sales team is about to have a conversation informed by what they see in Salesforce.

A small number of tools sit at the boundary between billing and the order it came from, or between billing and the customer who receives it.

For tenants collecting through Stripe, the server also covers the configuration that keeps the two systems describing the same thing in the same way. Field mapping is the substance of this: deciding which Nue field corresponds to which Stripe field, so information arrives where it is expected.

Billing questions rarely stop at the billing system. The Nue MCP Gateway federates every server behind one connection, so an assistant can follow a question wherever it leads without being reconnected.

In practice this means a query that begins with an unpaid invoice can move to the subscription that produced it through the Nue Lifecycle Manager server, and from there to the pricing that governs it through Nue Price Builder. Where an enquiry is simply about what a named customer owes, the Lifecycle Manager server already provides convenient customer-scoped views of invoices and credit memos, and is often the shorter path.