Skip to main contentSkip to footer

Implementer: Run IFS Cloud Projects From Registers

Implementer runs IFS Cloud implementations from registers, not files: gates, CRIM scope, migration, tests and approvals, with a 15-minute live demo.

Implementer · IFS Cloud implementation management Know who approved what, and on what evidence, in every IFS Cloud project Key takeaways A project kept in…

Read more

IFS Cloud Implementation Rescue: Diagnose, Decide, Recover

IFS Cloud implementation rescue for stalled projects: a diagnostic, a keep, repair or rebuild decision per area, and a dated recovery plan.

IFS Cloud implementation rescue · Independent IFS Cloud practice A stalled IFS Cloud project needs a diagnosis, a decision per area and dated gates The go-live…

Read more

IFS Cloud Reporting Tools: Quick Reports to Lobbies

IFS Cloud reporting tools in six layers: Quick Reports, Business Reporter, Lobbies, Power BI, Analysis Models and OData, and when to use each.

Independent IFS Cloud practice · Reporting From the weekly Excel export to a Lobby your team opens first Key takeaways IFS Cloud reporting tools fall into six…

Read more

Purchase Order Received but Not Closed in IFS Cloud

A purchase order line received in full can stay open in IFS Cloud. It lingers on open-PO reports and clutters them until someone closes it.

Independent IFS Cloud practice · Procurement The purchase order you received, and the line that never closed The goods arrived, the receipt matched, and every…

Read more

Purchase Order Short Receipt Left Open in IFS Cloud

Part of a purchase order arrives and the line stays open in IFS Cloud. An open remainder can keep counting as supply that is not coming.

Independent IFS Cloud practice · Procurement The purchase order that arrived half full and stayed open You ordered a hundred. Sixty arrived, the receipt was…

Read more

Purchase Order Over-Receipt in IFS Cloud

Goods can arrive in excess of the purchase order in IFS Cloud and pass inside a wide tolerance. How to list over-receipts before you pay for them.

Independent IFS Cloud practice · Procurement The delivery that brought more than you ordered, and nobody stopped it You ordered a hundred. A hundred and twenty…

Read more

Purchase Orders Priced Off Contract in IFS Cloud

A purchase order can be placed at a price the active agreement never authorised. The gap may surface only on the invoice. How to list it in IFS Cloud.

Independent IFS Cloud practice · Procurement The price you negotiated, and the order that ignored it There is an active blanket agreement on the part. Someone…

Read more

Purchase Order Currency Mismatch in IFS Cloud

A purchase order can carry a currency or rate that differs from the supplier default, so landed cost is off in IFS Cloud before the goods arrive.

Independent IFS Cloud practice · Procurement The order looked right in one currency, and cost the wrong number in another A purchase order in IFS Cloud carries…

Read more

Purchase Order Confirmation Mismatch in IFS Cloud

A supplier can confirm a purchase order at another quantity, price or date and the line still reads confirmed. How to list those gaps in IFS Cloud.

Independent IFS Cloud practice · Procurement The order you placed, and the confirmation that quietly changed it You raise a purchase order for a batch of…

Read more
Abstract illustration on a navy background with the article title: “Period End Close”

It is day four of the close, and finance is the only floor with the lights still on. The controller has a spreadsheet open that does not agree with the ledger, an email out to a cost centre that has gone quiet, and the same number in two reports that somehow changed between this morning and now. Ask her how it is going and she uses one word, the word every controller uses. Chasing.

A five-day close feels like a failure of finance, and finance is where the blame lands. But finance did not make this mess. It only inherited it, on a deadline, at the worst possible moment.

“

The close is a mirror. It reflects, at month-end, every shortcut taken upstream weeks earlier: in a warehouse, on a work order, nowhere near finance.

IFS Cloud can turn the close from a scramble into a controlled, repeatable sequence. But only if you treat it as the last mile of a clean pipeline, not as a finance sprint bolted onto the end of every month. Here is what a good close actually rests on, and why nearly all of it lives upstream of the people doing the chasing.

The ledger only reflects the sub-ledgers

In a suite like IFS Cloud, the general ledger sits downstream of everything (inventory movements, manufacturing cost, project transactions, purchasing accruals, sales invoices), each posting in through defined accounting rules. So the ledger is never cleaner than the transactions feeding it. That number the controller cannot explain? Manufacturing or the warehouse created it three weeks ago, and she is doing forensic accounting to account for their open work order.

The lever is not a faster finance team. It is sub-ledger discipline during the month: costed transactions, closed work orders, cleared accruals, reconciled inventory, done continuously, so that at period-end there is nothing left to chase because nothing was left open. The close gets fast when the month was clean, never when finance works the weekend harder.

Period control is a sequence, or it is theatre

IFS gives you real control over accounting periods: what can still post where, and in what order things close, so sub-ledgers settle before the ledger locks behind them. Used deliberately, it is a gate: late transactions land somewhere controlled instead of quietly reopening a number you already signed off. Used as an afterthought, it is a button someone clicks at the end, and then spends next month explaining why last month moved after it was closed. Decide the order on purpose. Which sub-ledgers close first, when the ledger locks, who may reopen a period and on whose authority. A close with no sequence is not a close. It is a snapshot that is still moving.

Two truths the system can carry, or two you carry by hand

Organisations of any size owe more than one accounting truth: a local statutory view and a group standard, different valuations, different calendars. IFS can carry them in parallel, natively, falling out of the same postings. The trap is treating that as something finance reconciles at the end with spreadsheets. Do that, and every close becomes a manual bridge between two views the system could have maintained all along, rebuilt from scratch, twelve times a year. Designed properly up front, both truths just appear. Bolted on afterwards, you have signed finance up to reconcile two realities by hand forever. It is an implementation decision, and it quietly sets the ceiling on how fast every future close can ever be.

You cannot speed up a close you cannot see

Part of why the close feels like chaos is that no one can see it. Twelve tasks across six people, and the only status report is walking over and asking. So the controller spends the week chasing status instead of clearing work, the priciest kind of busy there is.

“

You do not speed up a close by working harder inside a black box. You speed it up by turning the lights on.

IFS Cloud’s Lobbies make the close a live picture (reconciliations outstanding, sub-ledgers still open, exceptions, the cost centres that have not reported), on one screen everybody shares, with no external BI stack to stand up. When the whole team can see the same close in real time, the controller stops being a human switchboard and the bottleneck stops hiding. The thing actually holding up day four becomes visible to everyone at once.

The first close after go-live is the one that tells the truth

Every implementation has a moment of truth, and it is not go-live weekend. It is the first month-end on the new system, where migrated opening balances, fresh accounting rules, new cost structures and people still learning the screens all meet real numbers against a statutory deadline. Teams who prepare for it as an event (opening balances reconciled to a trusted number, the close steps dry-run, the first period-end staffed like a second go-live) sail through. Teams who treat it as “just another month” discover, live and on the clock, that an opening-balance assumption was wrong. If you are implementing now, put that first close on the plan as a named milestone with its own rehearsal. It is the exam the entire finance workstream was really studying for.

🧮

The close is the last mile of a clean pipeline

Every point above pushes the work upstream of period-end: into disciplined sub-ledgers, a deliberate sequence, parallel accounting designed once, a close you can see, a first month rehearsed. Do that and the close stops being five days of chasing. Skip it and no amount of heroics at month-end will save you, because the mess was already made, somewhere you were not looking.

Day one, the other version

Picture the same controller, a few months later. The sub-ledgers reconciled themselves through the month, because nothing was left open to chase. The sequence ran in order. Both accounting truths were already there. And the whole close sat on one Lobby the team could see, so nobody had to walk over and ask. The lights in finance are off by a reasonable hour, because the close finished on day one, not because anyone worked harder, but because the month was clean before it ever reached her desk.

That is the difference between a scramble and a sequence. It was never really a finance problem. It was a pipeline, and the close was just where you finally saw it.

Make the close fast because the month was clean

We design IFS Cloud finance and data governance so period-end is a controlled sequence, not a scramble, and so the first close after go-live is a milestone, not a crisis. If your month-end is five days of chasing, the fix is upstream, and we know where.

Fix the close upstream

ROI Calculator

Calculate your return on investment

Input Values

€
€
€

Results

Annual Savings
€ 0
Payback Period
0 months
ROI
0%
Monthly Savings
€ 0

Get Detailed Report

Enter your details to receive a detailed ROI report.