Reconcile Malta ARMS Bills Across Property Entities

To reconcile Malta ARMS bills across a property portfolio, keep a permanent property and account master, then append every extracted bill to a bill-level tab. Each bill needs to be coded by owner entity, property, tariff class, billing period, and tenant recharge status before the totals roll into the monthly close pack.

That is the part that gets lost when the work is described as "utility bill processing." Reading one ARMS bill is not the control problem. The control problem appears when the same administrator handles apartments, commercial units, holiday lets, and common areas owned by different companies and natural persons, while bills arrive on bimonthly cycles and tenants are recharged on lease terms that rarely match the ARMS period exactly.

The reconciliation has four axes:

• Owner entity: the company, partnership, trust, sole trader, or natural person whose books should carry the cost.
• Property or ARMS account: the physical unit, account number, service number, meter, or shared supply point that received the electricity or water.
• Tariff class: Residential, Domestic, or Non-Residential, with eco-reduction and resident details kept visible for review.
• Tenant or occupant: the person or business using the property during the bill period, and whether the cost is recharged, absorbed, included in rent, or allocated under a shared-meter rule.

For a small landlord with one or two flats, that might fit in a simple payment tracker. For a Maltese property manager, family office, or accountant handling ten or more properties across mixed ownership, it needs a proper close workflow. ARMS bills are supplier utility bills. They have to be extracted, coded, accrued, checked against tenant recharge invoices, and posted into the right books with enough evidence for a principal, accountant, or auditor to follow the trail.

Build the Portfolio Master Before Importing Bills

The portfolio master is the control table. Bill rows change every period; the master tells the workbook what each ARMS account means.

At minimum, keep one row per ARMS account, service, or meter relationship, depending on how the portfolio is billed. The useful columns are practical rather than theoretical:

• Account number
• Service number
• Meter number
• Property address
• Owner entity
• Owner entity type
• Tariff class
• Eco-reduction status
• Primary meter purpose
• Tenant at period start
• Tenant at period end
• Recharge method
• Exception notes

Owner entity type deserves its own column because Maltese property portfolios are rarely as tidy as the management chart suggests. One administrator may handle properties owned by limited companies, partnerships, trusts, sole traders, and natural persons. The same ARMS supplier appears across the portfolio, but the cost does not belong to one accounting ledger. It belongs to the legal owner whose books carry that property.

The master should also separate the ARMS account holder from the accounting owner where those differ. A property sale, transfer between family entities, or delayed ARMS update can leave the utility account in a previous name. The close should not silently follow the old account name if the cost economically belongs somewhere else. Record the mismatch, code the bill to the correct owner entity if the accountant has approved that treatment, and leave the account-name issue in the exception notes until it is resolved.

Recharge method is another master-data field, not something to guess from each bill. Use clear values such as direct tenant bill, landlord recharges actual cost, pro-rata shared meter, utilities included in rent, not recharged, or under review. That one field determines whether the bill later needs a tenant invoice tie-out or simply forms part of the owner's absorbed property cost.

This is the foundation for allocating ARMS bills per entity in Malta. If the master is weak, every later pivot looks precise while quietly carrying wrong property names, wrong legal owners, stale tenants, or missing tariff context.

Keep the Bill Tab Append-Only and Source-Traceable

The bill tab is not a working scratchpad. It is the transaction layer. Once an ARMS bill is extracted, its row should be appended and left intact so the workbook can always trace a close number back to the source bill.

The official ARMS bill booklet identifies the bill's account number, invoice number, invoice date, billing period, meter location, tariff and resident information, electricity and water consumption, eco-reduction, estimated-bill reversals, account history, and actual or estimated meter readings. Those are not just bill layout details. They are the raw controls a portfolio reconciliation needs.

A usable bill tab should capture the fields that come from the document and the fields stamped during reconciliation. A typical row includes source file, source page, invoice number, account number, billing period start, billing period end, reading type, electricity consumption, water consumption, electricity net, electricity VAT, water charge, service charge, eco-reduction, balance brought forward, account-history movement, total payable, due date, posted entity, recharge invoice reference, and variance to recharge.

Keep calculated close fields separate from extracted source fields. The source columns answer, "What did ARMS bill?" The reconciliation columns answer, "Where did we post it, how did we accrue it, and what tenant recharge did it tie to?" That distinction matters when someone later challenges a variance. You should be able to show whether the number came from the ARMS bill, the property master, an accrual formula, or a manual review decision.

If the portfolio has a handful of bills, a bookkeeper can type this data. At volume, the better control is to extract ARMS bills into structured spreadsheets first, then reconcile from consistent bill rows. The upstream workflow to extract Maltese ARMS utility bills to Excel owns the field capture detail; this reconciliation starts once those rows exist. Invoice Data Extraction fits that upstream step by converting PDFs or images into Excel, CSV, or JSON from a prompt-defined field list, with source file and page references retained for verification. It also supports large batches, so the same prompt can be reused when a portfolio close contains dozens or hundreds of ARMS PDFs.

Once the bills tab is stable, the rest of the workbook can pivot by entity, property, tariff, and month without reopening every PDF.

Split Bimonthly ARMS Bills Into Monthly Costs

ARMS bills are not designed around a property manager's month-end timetable. The bill period may run across two calendar months, arrive after close, or include an estimated reading that is corrected later. The reconciliation needs an accrual policy before the first pivot is trusted.

The cleanest method for a received bill is day-count accrual. Take the bill amount to be accrued, count the service-period days falling in each calendar month, and split the amount in that ratio. If a bill covers 61 days and 31 of those days fall in March, March receives 31 days of cost and April receives the remainder. The same calculation can be applied at total-bill level or to separate electricity, water, service charge, and VAT lines if the accountant wants that detail in the close pack.

When the month closes before the ARMS bill arrives, use a rolling-estimate method. Accrue the missing month from the most recent confirmed bill, usually on a daily average, then reverse and true up when the actual bill is received. The important control is not pretending the estimate is actual. Mark the accrual method, the source bill used for the estimate, and the reversal period.

Estimated readings need their own flag. If ARMS later replaces an estimate with an actual reading, the close pack should show whether the variance is posted in the period of the actual bill or pushed back into the estimated period. Either approach can be defensible if it is applied consistently and the accountant has approved it. What creates audit friction is a silent correction that changes prior utility cost without a policy trail.

Tenant changes use the same date logic. If a tenant moves out halfway through an ARMS billing period and the lease terms require cost allocation by occupation days, split the relevant bill period across occupants as well as across calendar months. Keep the move-in or move-out date in the recharge schedule so the allocation is visible.

For a deeper generic treatment of accrual mechanics, the broader guide to utility bill accrual methods is the supporting reference. In the Malta ARMS portfolio close, the practical rule is narrower: every bill row should state whether it is actual, day-count accrued, rolling-estimated, reversed, or pending true-up.

Keep Tariff Class Visible Without Retelling the Tariff Guide

Tariff class belongs in the reconciliation because it changes what the reviewer should question. The close does not need to re-argue the Residential, Domestic, and Non-Residential rules every month, but it should make those classifications visible enough that unusual bills are not buried in totals.

Residential bills need eco-reduction visibility. If the bill shows an eco-reduction, keep that line in the bill tab rather than netting it away without detail. A property manager or accountant may need to see whether the reduction was present, absent, or unexpectedly lost for the period.

Domestic-rated properties deserve a different review lens. In a letting portfolio, a Domestic classification can be legitimate, stale, or wrong depending on the registered persons and use of the property. The bookkeeper's job in the close is not to decide the tariff law. It is to preserve the classification, flag mismatches against the property master, and route them to the person who can correct the ARMS setup if needed.

Non-Residential bills should remain separable because commercial units can sit under different lease and VAT arrangements from residential apartments. A showroom, office, childcare premises, or mixed-use common area may be managed by the same property team but reviewed differently by the accountant.

Use tariff class as a diagnostic field in the close pack. Flag bills where consumption is high against the property's usual pattern, the tariff class does not match the master, eco-reduction status changes unexpectedly, resident information appears inconsistent, Form H, Form F2, or Form R evidence is missing from the property file, the pro-rata tariff-band context looks unusual, or a property moves between classes without an approved note. These flags do not stop the close by themselves, but they stop tariff questions being discovered months later during tax or tenant review.

The detailed tariff explanation belongs in the separate guide to ARMS Residential, Domestic, and Non-Residential tariff classification. In this workflow, tariff class is a reconciliation dimension: keep it visible, subtotal by it where useful, and send exceptions to the right reviewer.

Tie Landlord Utility Cost to Tenant Recharge Invoices

For recharged properties, the utility close is not finished when the ARMS cost is posted. The bookkeeper also has to show what was invoiced or allocated to the tenant and why any difference exists.

The control is simple in shape: compare ARMS billed to the landlord with the tenant recharge for the comparable period. The schedule should carry the ARMS account, property, tenant, bill period, recharge period, recharge invoice reference, recharge method, ARMS amount, tenant charge, variance amount, variance reason, and unresolved flag.

The variance reason is the field that makes the schedule useful. A difference can be legitimate when ARMS billed a bimonthly period but the tenant was recharged monthly, when a tenant changed during the bill period, when a shared meter is split by an agreed allocation key, when an eco-reduction is retained or passed through under the lease terms, when an administration charge is added separately, or when social tariff treatment affects the landlord's bill. Those are not the same as unexplained differences.

Do not let VAT treatment disappear into a spreadsheet note. The close schedule should show enough context for review, but the detailed legal and tax analysis sits outside the reconciliation workbook. When the recharge involves landlord-to-tenant billing, the supporting article on Malta VAT treatment of landlord utility recharges is the better place for the treatment detail.

Unexplained material differences should move to the exception queue. That might mean a missing tenant invoice, a recharge invoice posted to the wrong period, a shared-meter allocation not approved, an ARMS bill assigned to the wrong property, or a lease term that does not match the billing practice. A variance does not become harmless because the portfolio total agrees. If the landlord paid ARMS and the tenant was meant to reimburse the cost, the tie-out needs a documented answer.

Roll Up Costs by Owner Entity and Accounting System

Once the master and bill rows are reliable, the entity roll-up should be mechanical. Pivot the bill tab by owner entity and period, keep property and tariff class as secondary dimensions, and cross-foot the result to total payable plus any accrual or reversal entries.

That per-entity view is what a Maltese family office property utility bookkeeping process needs. One administrator may manage the full portfolio, but the accounting output cannot be a single blended utility total. Each legal owner needs its own subtotal because each has its own books, chart of accounts, VAT position, tax return, and review trail.

The posting pattern depends on the accounting system, but the dimensions are consistent. In Xero or QuickBooks, the ARMS bill may post as a supplier invoice to the owner entity, with the property carried in tracking categories, classes, locations, or project fields. In Sage, Shireburn, Indigo, or an accountant's working paper, the same idea may appear as cost centres, analysis codes, or separate schedule tabs. The label changes; the control does not. The bill must retain owner entity, property, tariff class, period, and recharge status after it leaves the reconciliation workbook.

For Xero per-property tracking, avoid using one supplier contact or one expense account as the only analysis layer. If every ARMS bill posts to utilities expense with no property dimension, the portfolio manager loses the ability to compare absorbed cost, tenant recharges, and exceptions by property. If every property is tracked but owner entity is weak, the accountant has the opposite problem: useful operational detail posted to the wrong books.

The exception queue should sit beside the roll-up, not after it. Common items include wrong owner entity, missing account mapping, shared meter awaiting an allocation key, estimated bill awaiting actual true-up, photovoltaic credit balance, missing recharge invoice reference, disputed tariff class, or an ARMS account still in a former owner's name. Give each item an owner, a reason, a financial amount, and an expected resolution date. Open exceptions can still be posted if the accountant approves the treatment, but they should not disappear from the close pack.

The Close Pack a Principal or Auditor Can Review

The close pack is the output of the reconciliation. It should let a principal, accountant, or auditor review the portfolio utility position without reopening every ARMS PDF or asking the bookkeeper how the workbook was built.

At minimum, include these schedules:

• Portfolio summary: bills posted, total electricity consumption, total water consumption, total net cost, VAT, eco-reduction, total payable, tenant recharge total, absorbed owner cost, and unresolved exceptions.
• Per-entity subtotals: one block for each legal owner, with period cost, accruals, reversals, recharges, and open items.
• Per-property detail: account number, address, tariff class, tenant status, bill period, total cost, recharge method, and posting destination.
• Recharge variance schedule: ARMS cost compared with tenant recharge invoice or allocation, with variance reason and unresolved flag.
• Exceptions schedule: wrong owner, missing master data, shared meter issues, estimated readings, tariff questions, PV credits, and missing recharge references.
• Estimated-versus-actual schedule: current and prior-period estimates, actual readings received, true-up amounts, and posting treatment.
• Tariff diagnostic flags: properties where the bill classification or eco-reduction status needs review.
• Accrual entry: the monthly journal or working-paper entry for bills not yet received, with reversal logic.

The pack should cross-foot in more than one direction. Bill-level rows should agree to per-property totals. Per-property totals should agree to per-entity totals. Tenant recharge totals should agree to the recharge variance schedule. Absorbed owner cost should agree to what remains after recharges. Open exceptions should agree to the unresolved items listed beside the roll-up.

This is the Malta property manager utility close checklist inside a broader accounts payable month-end close process. Start with the master, keep bill rows append-only, document the accrual and estimate policy, review recharge variances, then post only after exceptions are either resolved or carried forward with an owner and date. The close is not strong because the spreadsheet is complex. It is strong because each number can be traced back to a bill, an entity, a property, a tenant decision, or a documented open item.