Real Estate Property and Lease Management

The pain

SAP Business One knows how to invoice a customer. It does not know what a lease is. It has no concept of a building that contains units, a unit that is occupied for a fixed term, a rent that steps up 5% on each anniversary, a security deposit that must be returned less deductions, or a tenant who handed over twelve post-dated cheques at signing.

So property companies run the business in spreadsheets and use SAP only as a ledger. The rent roll lives in one workbook, the cheque register in another, and someone raises A/R Invoices manually every month by copying last month's. The consequences are predictable: an escalation clause that everyone forgot, so a unit bills at the year-one rate for three years. A cheque that was never presented. A lease that expired without a renewal conversation. A deposit refunded in full because nobody recorded the damage deduction. Occupancy figures that are a guess because no system holds the vacancy dates.

And because the rent roll is outside the ERP, the finance team cannot answer the two questions that matter — what is contracted revenue for the next twelve months, and which of it is at risk — without rebuilding both spreadsheets.

What ECOSIRE builds

We build a SAP Business One add-on that puts the property portfolio inside the ERP, using SAP's own extensibility so leases, units and cheques are first-class records that post through standard finance rather than around it.

Property and unit master

Properties, buildings, floors and units are modelled as User-Defined Objects with their own forms and searchable lists. Each unit carries its physical attributes — area, type, bedrooms, parking allocation, fit-out status — plus its commercial attributes: market rent, current lease, and status (vacant, reserved, occupied, under maintenance, legally blocked). Units link to the SAP structures your finance already uses, so revenue can be posted against the Cost Centre or Project dimension that represents the building, and reported in standard financial reports without a separate reporting tool.

Tenants as Business Partners

Tenants are real SAP Business Partners, not a parallel list. UDFs on OCRD carry the tenant-specific data — identity document, nationality, emergency contact, guarantor, tenancy history — and every rent invoice, receipt and deposit is an ordinary SAP document against that Business Partner. This matters: credit control, aging, statements and dunning all work out of the box because nothing was re-invented.

Lease contracts and schedules

A lease is a UDO record linking a unit to a tenant for a term, holding rent amount and frequency, payment method, grace period, service charges, chargeable utilities, renewal option, notice period and break clause. From that contract the add-on generates a rent schedule — the explicit list of every billing period across the whole term, each with its due date, base rent, service charge and tax treatment.

That schedule is the heart of the system. Because every future period exists as a row before it is billed, you can report contracted revenue by month, see exactly what an escalation will do before it happens, and pro-rate a mid-month move-in or an early termination against real numbers instead of a manual calculation.

Escalation clauses

Escalations are modelled explicitly: fixed percentage on each anniversary, fixed amount, stepped schedule with different rates per year, or index-linked with the index value entered when published. When an escalation fires, the add-on regenerates the affected future schedule rows, records the previous and new values with the user and timestamp, and leaves already-billed periods untouched. Escalations due in the next period appear in an approvals queue so a person confirms the new rent before the first invoice at the new rate is raised.

Recurring rent invoicing

A scheduled run picks up schedule rows falling due and creates A/R Invoices through the DI API and Service Layer — correct Business Partner, correct revenue account per charge type, correct tax code for your localisation, correct Cost Centre or Project dimension for the property, and the lease reference on the document. Rent, service charge, parking, utility recharges and one-off charges post as separate lines to separate accounts so the P&L separates rental income from recoveries. Runs are previewed before posting, and the batch is reversible before release.

Post-dated cheque management

Post-dated cheques get a full register: cheque number, bank, branch, amount, cheque date, the lease and schedule periods it covers, and its physical location. Status moves through received, in safe, deposited, cleared, bounced, replaced or returned, and each transition posts the correct SAP entry — deposit into the bank clearing account, clearance to the bank account with the A/R Invoice settled by Incoming Payment, and a bounce reversing the settlement, posting the bank charge and flagging the tenant. A dated report tells the finance team exactly which cheques to bank this week, which is normally the single most manual task in the whole operation.

Deposits, renewals and handover

Security deposits are tracked as a liability against the tenant with their own account, and refunds are processed against a deduction worksheet — damages, unpaid utilities, cleaning — producing the net Outgoing Payment and the associated charges. Renewal and expiry alerts fire on your notice-period rules so a lease never lapses unnoticed. Move-in and move-out handovers capture meter readings, condition notes and attached photographs against the unit.

Reporting

Crystal Reports ship for rent roll, occupancy and vacancy by property, expiry pipeline, escalation forecast, cheque due list, arrears aging by tenant and unit, and contracted revenue by month. Because everything posts through standard SAP documents, the same numbers appear in standard financial reporting.

Who it is for

Property owners, landlords, developers with a retained portfolio, facility operators and mixed-use asset managers running SAP Business One 10.0 who currently keep the rent roll and cheque register outside the ERP.

How delivery works

1. Scoping call. We walk your portfolio structure, lease types, escalation clauses, charge types, tax treatment, cheque process and approval rules. 2. Fixed quote. A written scope naming every object, screen, posting rule and report, at a fixed price. 3. Build. Development against a copy of your company database, with your real charge structure and chart of accounts. 4. Install in test. We install into your test company, load a sample of real leases, and run a full monthly cycle — generation, escalation, invoicing, cheque banking, a bounce, a termination. 5. Install in production. Installation, migration of your existing leases and open cheques from your current spreadsheets, and a supervised first live billing run. 6. Support window. A defined post-go-live period covering defects, rule adjustments and the first renewal cycle.

Lead time is typically 2–4 weeks from signed quote, longer where several localisations or unusual lease structures are involved — we will say so in the quote rather than after. This is built to order: there is no download, no trial version, and no pre-existing product. You receive an add-on shaped around your portfolio and your lease terms.