Intercompany trading

The same order, typed twice

When two companies in your group buy from each other, someone re-types on one side what was already entered on the other. cifraHQ creates the seller's sales order the moment the buyer releases the purchase order.

Available
  • Both companies opt in explicitly
  • The seller sells at its own prices and taxes
  • The buyer's PO number travels with the document
  • If the sync fails, both sides are told

The cost of typing it twice

Two companies in one group, two systems, and a single order entered by two different people.

Quantities that do not match

The most common error between sister companies is not an accounting one. It is a typo in a quantity when the order is keyed a second time.

The hand-off lives in email

The order travels by email, chat or spreadsheet before it exists in the seller's system. None of that can be audited.

The seller finds out late

The company that ships cannot see the order until someone keys it in, and the delivery date absorbs the lost time.

Nobody knows which order is which

With no shared number across the two documents, matching which order belongs to which is manual work at close.

With intercompany trading

The order is entered once, in the company that is buying.

Copied, not re-keyed

SKUs, quantities and pack sizes arrive on the seller's order exactly as entered. There is no second chance to get them wrong.

The hand-off stays in the system

The sales order is created in the seller's tenant when the purchase order is released, with no email in between.

The seller sees it immediately

The order appears in the shipping company the moment the buyer releases it.

One number links both sides

The seller's order shows the buyer's PO number, and the buyer's PO shows the seller's order number.

How it works

Nothing crosses between two companies unless both of them agreed to it first.

1

Both sides opt in

The buyer marks the vendor as a sister company. The seller marks the customer as a sister company. Without both marks, nothing crosses.

2

The buyer releases the PO

An ordinary purchase order. If the vendor is not a group company, it behaves exactly as it always has.

3

The sales order appears

In the seller's tenant, with its prices, its taxes, its warehouse, the buyer's delivery address and the buyer's PO number.

4

Both sides stay traceable

Each document points at the other and shows the sync status at all times.

Buying company
Releases the purchase order
automatic
Selling company
Receives the sales order

Each company keeps its own books

The only thing that travels is order content: SKUs, quantities, pack sizes, the delivery address and the buyer's PO number. Nothing else.

The two documents may not match in value

And they should not. The seller prices with its own price lists and settles with its own taxes, because it answers to its own accounts and its own auditors. cifraHQ does not force two companies to share figures.

Seller's prices

The seller applies its own price lists and rules. It does not inherit what the buyer put on the purchase order.

Seller's taxes

Taxes come from the customer and product tax codes held in the selling company.

Seller's warehouse

The seller picks and ships from its own warehouse, on its own payment terms.

Each ledger in its jurisdiction

Every company closes with figures that are correct for the country it files in, without dragging in the other side's.

A failed hand-off is never silent

The purchase order carries the sync status on the document itself.

Pending Synced Failed Conflict

If the hand-off fails it shows on the document and raises a notification. Nobody finds out three days later because the order never arrived.

Purchase order
Buying company
StatusSynced
Seller orderVisible
PricingBuyer's
Sales order
Selling company
OriginIntercompany
Buyer POVisible
PricingSeller's

Changes before shipping

While the seller's order is still draft, the buyer's changes sync across on their own.

Held on draft

If the buyer sends the PO back to draft, the seller's order is held and the seller cannot release it.

Conflict after release

Once the seller has released its order, a later buyer change raises a conflict and notifies both sides instead of altering the document.

No surprise deletions

A purchase order cannot be deleted once the seller has released its counterpart.

What it does today, and what comes next

We would rather tell you exactly where the feature stops today.

Available

Purchase order to sales order

  • A released purchase order creates the sales order in the sister company.
  • Explicit opt-in on both companies, per vendor and per customer.
  • The seller applies its own prices, taxes and warehouse.
  • Status on the document and a notification when something fails.
  • Draft changes sync, plus hold and conflict handling after release.
On the roadmap

Not available yet

  • The seller's delivery creating the buyer's receipt.
  • The seller's invoice creating the buyer's vendor bill.
  • A reconciliation report showing open pairs and quantity or value differences across the group.

These three are in development and are not part of what ships today.

Works alongside LogisticaHQ

Both companies can run on the same warehouse system as separate clients. Each document goes to the client it belongs to.

Stop entering the same order twice

If your group has two or more companies that buy from each other, we will walk the whole hand-off through your own operation.