Connecting the work around every bond.

The operational challenge

The record is only the beginning.

A bond carries a case number, parties, dates and premium terms. Those details matter again when someone prepares a document package, processes a renewal, sends an invoice or applies a payment. Each step has its own rules, but each depends on the same underlying relationships.

The engineering challenge was to make that context useful across the application. A principal can have an attorney and law firm. A bond has a surety company, an office and important dates. Billing introduces recipients and delivery preferences. These relationships need a clear place in the data model so the next workflow can use them.

The application

A shared foundation for different kinds of work.

We connected a React and TypeScript staff interface to Java services and a relational bond model. Staff can search for a bond, create or update its details, maintain related parties and move into its invoice history or ledger. The interface groups bond management, accounting, reporting and administration into distinct work areas.

Saving a bond does more than store form fields. The backend validates the request, saves the bond, maintains principal and obligee links, and records invoice recipients. Updates also check field permissions and resolve the recipients that billing will use.

Microsoft identity supports sign-in. Route permissions shape the available workspace, while backend permission checks protect the corresponding operations. Separate permissions cover actions such as posting or reversing a cash receipt.

Documents and background work

Give every package a visible path to completion.

Document preparation begins with the bond context and a selection of reports. The application validates the request, records a job and places it on a queue. A worker generates the selected documents, while the staff interface can check progress and retrieve the results.

Civil and probate document paths use templates and the relevant bond information. Output can be prepared as PDF or Word documents, returned through a download link or passed to the email workflow. The job records full success, partial success or failure, so a package with an incomplete result has a distinct state.

Azure Service Bus connects the background work, and Azure storage holds generated downloads. Scanned-file access connects to Dropbox. Microsoft Graph provides an email integration that handles attachments and the sending employee’s context.

The financial workflow

Carry the bond through renewal, billing and receipt.

Renewal processing starts with qualifying bonds and their anniversary dates. It prepares invoice terms, checks for overlapping terms, creates invoices and associated ledger entries, resolves recipients and assigns delivery batches. Updating the anniversary is one part of that connected process.

Receipt entry has separate validation and posting steps. When a receipt is posted, the backend locks the referenced invoices, updates paid and open amounts, saves ledger entries and updates the related bond status. Posting a receipt is a defined step with its own validation, separate from the follow-up work.

Reporting brings those records back into view through aging, renewals, cash receipts, ledger summaries and other operational reports.