Browse articles
- Getting started
- Project finances
- Billing by the hour
- Practice finances
- Grouping fees
- Budgeting project costs
- Claim an expense
- Recording revenue entries
- Recording project expenses
- Purchase orders
- Approving expenses
- Going further
- Construction cost fees
- Recurring fees
- Billing expenses
- Contingencies and discounts
- Billing progress claims
- Project templates
- Overheads
- Getting started
- Billing milestones
- Sending an invoice
- Billing logged time
- Month-end invoicing
- Fee proposal templates
- Writing a fee proposal
- Getting a proposal signed
- Link invoices that are already in Xero
- Going further
- Payments and overdue invoices
- Connect your accounting system
- Fee groups on invoices
- Tax codes and accounts
Office billing details
Let an entity issue invoices, quotes and purchase orders under its own legal name, ABN and logo, falling back to the organisation wherever a detail is left blank.
What you'll achieve
Set up a billing profile so an entity's documents print under its own legal identity instead of the organisation's, and understand why that identity never changes after the fact.
You'll end up with: An entity with its own legal name, ABN, address and payment details where they differ from the organisation, and every document raised against it correctly stamped with that identity for good.
Before you start
Nothing about a billing identity is all-or-nothing
An entity's billing profile is a short list of document-facing details: a logo, legal name, ABN, phone, business address, email, website and payment details. Every one of them falls back to the organisation independently. An entity can differ from Northlight Architects in nothing at all, in only its ABN, or in every field, whatever actually matches how the studio trades. There's no toggle that switches the whole profile on or off; leave a field blank and that one field alone inherits the organisation's value, the rest of the profile is unaffected.
Sydney Office trades as its own registered business with its own ABN, but shares Northlight's logo and head-office phone number. That's the profile below: two fields filled in, everything else left blank on purpose.
- 1
On the Entities tab in Settings, open the cog at the end of Sydney Office's row and choose Edit. Editing an existing entity is what reveals its Billing profile section; a brand-new entity only asks for a name and code.
- 2
Enter the Legal name and ABN for Sydney's own business.
- 3
Leave Phone, Business address, Email, Website and Payment details blank, so they keep inheriting Northlight's organisation-wide values.
- 4
Click Save changes.
Each field's placeholder reads the organisation value it'll fall back to, Falls back to organisation: Northlight Architects, for instance, so you can see exactly what an empty field resolves to before you save.
Documents remember the entity they were raised for, permanently
The moment an invoice, quote or purchase order is created, Monument stamps it with an entity, its project's own entity by default. With more than one entity active, the create screen also shows an Entity picker defaulting to that same value, so you can raise a document under a different studio than its project when that's genuinely what happened, without that choice touching the project itself. Whichever entity ends up on the stamp never changes again, even if the project is later reassigned to a different entity. A legal document can't retroactively change who issued it, so Monument doesn't let it: the identity that prints on a document, and the identity a client's payment or an accounting sync resolves against, always comes from the document's own stamped entity, resolved field by field against that entity's billing profile with the organisation as the fallback.
Move a project from one entity to another and only documents raised after the move pick up the new identity. Every invoice, quote and purchase order already issued keeps printing under whichever entity was responsible for the project the day it was created, exactly as a paper invoice already sent can't un-print itself.
This is also why a firm that adopts billing profiles partway through stays consistent with its own history: documents raised before any billing profile existed keep showing the organisation's identity, because that's genuinely what was true when they were issued.
Give an entity its own invoice numbering, if you need it
By default, every entity shares one invoice sequence firm-wide, INV-042 is followed by INV-043 no matter which entity either one belongs to. Once a second entity exists, an opt-in setting lets each entity keep its own sequence instead.
- 1
Open Settings, go to the Invoices & accounting tab, and find Invoice numbering. Choose Sydney Office in the entity tabs; Accounting and Payment details follow the same selection.
- 2
Review Sydney’s inherited invoice pattern and Next preview, then switch on Separate sequence per entity.
- 3
Save. Each entity now starts and maintains its own invoice numbering from here on.
This toggle affects the shared invoice sequence setting. You can also edit an entity’s own invoice, quote or purchase order pattern and starting number in its tab. An entity invoice override uses a separate sequence automatically. Use organisation setting removes an entity override when you want to share the pattern again.
Payment details sits at the bottom of Invoices & accounting. Its entity tabs follow the same selection as Invoice numbering. Leave Sydney’s inherited payment details unchanged in this example. A practice with one entity sees no entity tabs.
Troubleshooting
- A document shows the organisation's logo or address, not the entity's. That field is deliberately blank on the entity's billing profile, so it's falling back to the organisation exactly as designed, not failing to load.
- I don't see an Entity field when creating a document. It only appears once a second active entity exists. With just one entity there's nothing to pick between, so the document stamps with it automatically.
- I reassigned a project but its old invoices didn't change. That's correct. Entity stamping happens once, at creation, whether you picked it explicitly or it defaulted from the project, and is immutable from then on. New documents raised against the project from now on will use the new entity; nothing already issued does.
- Invoice numbers reset or jumped after turning on per-entity sequences. Each entity starts its own counter once the toggle is on. Choose each entity tab and check its Next preview in Invoice numbering before relying on a specific number.
Where this fits next
Billing identity is set at the entity level; the same entity split reaches further once it's in reports and connected to your accounting system. See Reports by office for filtering and grouping by entity, and connecting a separate accounting system to a single entity rather than the whole firm.
Search Monument help
Search help articles and open a result.