Managing Sender and Recipient Profile Masters

Introduction

The information on a document isn't just line items. There's the biller — your own company name, address, and bank details — and the recipient — the customer's company name, address, and addressee. This "cast of characters" is always present.

And it barely changes from one transaction to the next. You bill the same customer at the same address, to the same addressee, every time. Yet typing all of this by hand for every document is both a waste of time and a breeding ground for mistakes.

This article covers a design that manages biller and recipient information centrally as masters, keeping per-document input to a minimum.

The Waste of Typing Company Info Per Document

The contradiction of retyping what never changes

A common sight in template workflows: copy-pasting your own bank details and the customer's address every time you make a document.

Think about it — your company info doesn't change several times a year. Neither does a customer's address. Transcribing information that rarely changes, on every single document — that's plainly contradictory.

And as long as you're typing by hand, mistakes are unavoidable. A single digit off in the bank account number, a missing honorific on the customer's addressee. Errors like these bear on the trust your counterpart places in you.

The problem of scattered information

The other problem is that company info ends up scattered inside document files.

When information is embedded in each file, you can't keep track of "where do I need to fix this?" when a change happens. It's the inevitable fate of copy-based workflows.

The Idea of a Profile Master

Hold the biller and recipient separately

The solution is to detach company info from documents and make it independent as a profile master.

There's basically one biller (your company), but there are as many recipients as you have customers. Manage these two kinds of profile separately, and making a document comes down to just choosing "which recipient."

Documents merely "reference" the master

The crux of mastering is that a document references company info rather than holding it.

A document is really just "line items" plus "which profile to use" as reference info. The company info itself lives on the master side. So there's no need to type company info when making a document — pick the customer, and the address and addressee fill in automatically.

How Mastering Changes Operations

Minimal input, zero mistakes

Introduce a profile master and the input fields for creating a document drop dramatically.

What the operator enters is only the information that truly varies per transaction — that is, the line items. Transcription errors in company info become structurally zero.

Fix once, apply everywhere

The greatest benefit of mastering is that it's resilient to change.

Say your bank account changes. With a master, you fix one place — the biller profile. Every invoice generated afterward comes out with the new account. No more hunting through old templates.

The same goes for when a customer relocates and their address changes. Just update the relevant recipient profile. Precisely because the information lives in one place, the cost of change is small.

Conclusion

Managing sender and recipient profile masters is a humble design with an outsized effect. Detaching company info from documents and managing it centrally as masters produced these changes:

• Input at document-creation time can focus on line items, eliminating transcription errors in company info
• Changes to bank details or addresses apply to all documents by fixing a single master
• Because information isn't scattered, you avoid the accident of sending stale info

With the data organized this way, Japanese rendering is supported by the technique in Japanese Font Embedding and File-Size Optimization, and storage of generated PDFs by the mechanism in Storing Generated PDFs and Designing Reissue. For the big picture, see Automated Invoice & Delivery-Note PDFs.