More Than One Entity in One Business: Separating Records and Documents

Many businesses run more than one entity - a registered sole trader alongside a company, two companies for two lines of activity, or a partnership added to an existing business. Whether the structure is right is a question for the accountant; what lands on the owner is the operations: which document goes out in whose name, and which account the money left from.

What actually has to be separate

The list is shorter than it seems, and every item on it is a decision point rather than a habit:

• Invoice and document numbering - a separate series per entity.
• Bank account - one per entity.
• Payment methods - a card or digital wallet belonging to one entity.
• Customer and supplier files, where the counterparties are not identical.
• Dealings with the authorities and the registration numbers.
• The accounting record, including how shared expenses are split.

The last item is the only one requiring professional judgement: how an expense serving both entities is split - rent, software, a vehicle - and what is needed to document the split. That is a question for the accountant, and the operational job is only to make sure their answer is actually applied, consistently.

The point that breaks first

It is nearly always the payment method. The owner holds one card, buys software on it, and the software serves both entities - or worse, only the second one. At the moment of purchase it looks trivial, and at year end it is a line that needs explaining.

The operational fix is not discipline but structure: a separate card per entity, even if one of them sees three transactions a month. The running cost of a second card is lower than the hours needed to unpick a mixture after the fact, and it also makes the monthly reconciliation simple.

What may actually be shared

The first row is the surprising one: there is no operational problem running one CRM for two entities, as long as a field marks which entity each deal belongs to - and every report filters on it by default. What breaks things is a report showing both entities together without anybody realising.

What it looks like on a document sent to a customer

The simple check is to look at an invoice, a quote and a contract issued this month and ask of each: which entity appears here, and is that the entity that received the money. A gap between the two is the most common problem at businesses with more than one entity.

What prevents it is tying the entity to the document rather than to the person. When the quoting and invoicing system holds a template per entity - with the name, registration number, account details and email signature - separation happens by itself and does not depend on somebody remembering to change a field. At a business using quotes and digital signatures, the same applies to the signature templates.

When a customer pays the wrong entity

This happens at every business with two entities, usually for a simple reason: the customer has account details saved from two years ago and pays where they have always paid. The money lands, the invoice sits open at the other entity, and nobody notices until the reconciliation.

What prevents it is not a reminder but what is printed on the document: the account details appear on the invoice itself every time, rather than in a one-off message sent once. When the details are on the document, the customer copies from the current document.

Once it has happened, the correction is not a bookkeeping action but a question for the accountant - a transfer between entities is a movement that needs documentation, not an "internal transfer". What is operational is marking the invoice immediately as paid-at-the-other-entity, so no collection reminder goes out while the money is already in.

Three monthly checks

1. That every invoice issued this month came from the right entity's series.
2. That every transaction in every bank account belongs to the entity that owns the account.
3. That every shared expense was split by the rule the accountant set, not by convenience.

Three checks, ten minutes in total, and they find almost everything that would otherwise surface at year end as two hours of decoding. The second is the important one: it is the only one that catches a card that slipped back into shared use.

What do you do when everything is already mixed?

That is the common state, and the question is where to start. The order that works is not to fix backwards but to cut forwards: set a date from which each entity operates fully separately, and leave the period before it to the accountant.

What matters before that date is preparing the infrastructure - accounts, payment methods, document templates, and an entity field in every system - so that the cut is a one-day event. A cut announced before the infrastructure is ready produces two months of half-separation, which is worse than two mixed entities.

Sources

• Israel Tax Authority - information for businesses
• Israel Corporations Authority
• The VAT period routine
• Book a call