Lynne MuyanoSAP Real Estate · lease design & lease data · remote
Property, retail and franchise businesses on SAP

The lease decisions nobody argued about are the ones you pay for.

Object granularity, recovery basis, how turnover rent settles. Each gets decided in a two-hour workshop by whoever answers fastest, and each one sets a running cost your finance team will carry for a decade. Nobody prices them at the time, because at the time they don't look like money.

Sectors
Developers, REITs, mall and estate operators, franchise and retail networks. Anyone whose balance sheet is mostly a lease book.
Clients
Programme owners who want lease design held on their own side of the table. And implementation partners who need RE-FX depth on a bid or a build. I work on my own or inside your team, whichever the work calls for.
Delivery
Remote, wherever you are. If you'd rather, the work runs inside your own tenant, so your documents never leave your control.
What those decisions cost, two years on

Nobody calls it a defect. It just shows up in the payroll.

These are composites of what property and retail finance teams tell me. Not quotes from named clients.

“Every month my team rebuilds the turnover rent computation in a spreadsheet. Every single month. We went live two years ago.”

Finance manager, mall operator

“The CAM reconciliation takes most of February. Three people, every year, for as long as I have been here.”

Controller, mixed-use estate

“I asked for occupancy by tenant across the portfolio. Eleven days and three people, and I still didn't fully trust the number.”

CFO, listed developer

“We found amendments that had never made it into the register. Two hundred of them, after go-live.”

Finance systems lead, developer

“Nobody can tell me which store leases expire next quarter without someone opening a folder. We paid a great deal of money not to have folders.”

Head of property, franchise network

“Audit asked about the lessor side. We had done the lessee side properly. That was an uncomfortable meeting.”

Finance director, REIT

Add those up and they're a permanent line in your operating cost. One that never appears in the business case.

And the fix gets dearer the longer it waits. Changing a lease hierarchy after go-live isn't configuration — it's a second migration, at second-migration prices, with a year of parallel reporting while you prove the numbers still tie. Caught at blueprint, the same decision costs an afternoon.

Five things to check before you sign

Each of these has a price attached.

You can check all five in about a week. Each one takes roughly a decade to undo, and pays for itself the whole time.

01
How does turnover rent settle inside the system? Percentage rent needs sales data to calculate. When that integration turns out to be hard, settlement quietly moves to a spreadsheet and stays there. Every store, every month.
02
Where does the annual CAM reconciliation actually run? If common area charges are modelled as a flat billing line instead of a recoverable, the annual true-up never automates. It just becomes something finance does every February.
03
Does your lease register still match your lease documents? Registers drift. Terms get updated in one place and not the other, amendments never make it in, expired leases stay open. Whatever's in there on migration day is what the new system will believe, permanently.
04
Can you show lessee and lessor treatment in one company code? Property and franchise businesses are usually both at once. One side tends to get configured carefully and the other left for later. Later usually means the audit.
05
What happens to the fit-out schedule on an early renewal? If capitalisation is tied loosely to a term that can change, it'll reconcile perfectly on day one and then drift a little every year after.

If any answer involves a spreadsheet, that's a running cost someone signed you up for without telling you. It's worth knowing the number before you accept it.

If two or three of them land uncomfortably, that's what the engagements below are for.

Who is writing this
Lynne Muyano
Lynne Muyano
Independent SAP RE-FX consultant

I'm Lynne Muyano, and I work on lease portfolios in SAP.

I have been doing SAP Real Estate since 2009 — fourteen full-cycle implementations, nine of them property or store-lease portfolios, across the Philippines, Singapore, Vietnam and Indonesia. Developers, mall operators, franchise networks, investment houses.

Before going independent I spent three years as a solution architect and programme leader inside an SAP consulting firm. That is where I learned what quietly gets traded away when a delivery schedule tightens, which is most of what I am useful for now.

I work as an independent contractor. Not a firm with a bench, not an agency placing someone else — one person you engage directly, on a contract for a defined piece of work.

I take a small number of engagements at a time, which means you get the person whose name is on this page rather than a team assembled after you sign. Some of this work is best done quietly on my own. Most of it isn't — it's done sitting with your finance and property people, or inside your delivery partner's team, arguing the design out loud until it holds. I'm comfortable either way, and I'll say plainly which one I think your programme needs. If that isn't me, I'll tell you that too.

  • SAP Real Estate since 2009, EHP 6.0 through S/4HANA
  • Fourteen full-cycle implementations, nine of them property portfolios
  • IFRS 16 lease accounting in SAP Real Estate — lease classification, right-of-use assets and liability measurement
  • Financial accounting, controlling, asset accounting and project systems
  • Configuration, data migration and cutover — including one legacy property migration with no data issues
  • TOGAF Enterprise Architecture Practitioner · PMI-certified project management
  • Working remotely across time zones
Engagements

Four ways to work with me.

Four engagements, separately priced, and none of them commits you to the next. The first three are done-for-you — you hand me the work and I hand back the result. The fourth is the opposite: me in the room, holding the line, while somebody else builds.

01

Lease dataAI-assisted

Priced by portfolio or by volume · starts next week · any programme stage

Know what you actually have. You send the documents and the register. I hand back structured, verified, load-ready data — and an honest account of what was wrong with it. This doesn't depend on where your programme is, and it has to be right before anything else works.

IncludesPortfolio data quality audit · lease abstraction into SAP-ready structured data · migration reconciliation, legacy against loaded, field by field

You get
  • A written account of what's really in your register — duplicates, missing end dates, expired-but-open records, terms held as free text a system can't compute
  • An extraction schema and field dictionary mapped to your RE-FX objects
  • Structured lease dataset, every field citing the document and clause it came from
  • An exceptions register — missing annexes, superseded amendments, contradictory terms
  • Load-ready migration file, and full-population reconciliation evidence your steering committee can sign off against

What it needs from youAn export, document access, and one workshop to agree the schema. No lease reading by your team at any point. If you'd rather, all of it runs inside your own tenant.

02

Lease designAI-assisted

3–5 weeks · fixed fee · before blueprint sign-off, or after go-live

Get the model right. The architecture you should be buying, written down before anyone builds against a different one. If you're already live, the same work runs backwards — every workaround named, costed, and a plan to fix it.

IncludesLease design review before blueprint · or live system assessment if that window has closed

You get
  • Target-state lease and property architecture, written for finance to read, not only IT
  • Lease classification and IFRS 16 treatment agreed before build — right-of-use assets, liability measurement, and how modifications and renewals are meant to behave
  • A lease model specific to your portfolio — object granularity, contract structures, recovery and settlement treatment
  • A decision register of what's already been settled and what needs revisiting
  • A written assessment of your partner's proposed approach
  • If you're live: every manual workaround costed in hours and headcount, with a remediation plan sequenced by cost of delay

What it needs from youSix to eight conversations across property, finance and IT. An hour each, nothing to prepare. I do the reading, the reconciling and the writing.

03

RE-FX implementation

Full-cycle · blueprint through hypercare · fixed scope or embedded

Have it built, properly, the first time. If you need the lease workstream actually delivered and not only designed, I take it end to end — blueprint, configuration, testing, migration, cutover and hypercare. This is the work I have done fourteen times.

ScopeThe RE-FX workstream and everything it touches — not your whole SAP programme. Your partner or your own team still delivers finance, procurement and the rest. I own the lease side and integrate to theirs.

You get
  • Lease and property solution design, configured — object hierarchy, contracts, conditions, recoveries, settlement
  • Integration built and tested to finance, controlling, asset accounting and project systems
  • Test scenarios drawn from your actual clause variety, executed rather than handed over as a template
  • Lease data migrated, reconciled and signed off
  • Cutover and hypercare on the lease workstream
  • Knowledge transfer to your team, so you are not dependent on me afterwards

What it needs from youA system, a sandbox, and someone empowered to make the finance decisions RE-FX posts into. Everything else is mine.

04

Design authorityAI-assisted

Monthly retainer · 6–8 days a month through blueprint, 3–4 through build

Keep it right while it's built. This one isn't done-for-you — it's me in the room. I sit in the design workshops that touch property and finance, approve or reject the lease design, and judge scope changes against the architecture rather than against the schedule. Then I stay through build and cutover to make sure what gets built is what was approved.

IncludesDesign authority through blueprint · build and cutover assurance

You get
  • Written sign-off or rejection on every lease-related design document, with reasoning
  • A maintained decision log, still legible when your partner's team rotates
  • Chairing of the architecture review board, or its equivalent in your governance
  • An independent view on every variation order touching property scope
  • Test scenarios drawn from the clauses actually in your portfolio, not three sample leases
  • Cutover readiness from the property and finance side, and a handover pack your own team can maintain

What it needs from youA seat at the design workshops and a reporting line to your sponsor. That's the whole point of it — without those two things this is an opinion rather than an authority.

For implementation partners

All four are available to you as subcontracted workstreams.

If you've won property scope, or you're chasing it, and you can't staff RE-FX — I contract in to cover it, without you carrying a permanent head. On a bid, I write the lease workstream and you drop it into your proposal. Named as a specialist or entirely behind your brand, whichever works better for the client and the evaluation.

No onboarding, no ramp-up, no recruitment cycle. A scope conversation and a point of contact is enough to start — and I'm happy to sit inside your team and your governance rather than beside it.

Not sure which of these you need?

That's usually the right place to start. Thirty minutes, and no proposal afterwards unless you ask for one. I'd rather tell you which engagement is worth having than sell you three.

Book thirty minutes
Terms

The same on every engagement.

  • Named person. The work is mine, and nobody gets substituted in later. Working alongside your team or your partner's is welcome; handing the work to someone else isn't.
  • Separable. No engagement commits you to the next one, and there's no discount for bundling.
  • Client-side work is contracted directly to you, never through your implementation partner.
  • Sponsor reporting. On design authority I report to your sponsor, with a written right to take a design decision to the steering committee.
  • No exclusivity, no non-competes.
Conflict rule

I don't hold two sides of the same programme.

Building the lease workstream and independently governing it are different jobs, and so are working for you and working for your implementation partner. Mixing either pair on one programme would make the independent half worthless, so I have written the boundary down rather than leaving it assumed.

  • I never act for a client and their implementation partner on the same programme.
  • I never review the work of a partner who's engaging me elsewhere.
  • If I built it, I don't also sign off on it as your independent authority. You would want someone else for that, and I will say so.
  • Anything that looks like a conflict, I tell you before scoping. If there is one, I turn down the second engagement.

Engaging me on the client side and want to know which partners I'm working with? Ask, and I'll tell you.

How your documents are handled

Where AI is used, where it is not, and where your files sit.

The engagements marked AI-assisted use automated extraction and analysis for the first pass. The design judgment, the checking of anything low-confidence, and every conclusion in a written deliverable are mine.

  • What I'd prefer — inside your tenant. If you're on Microsoft 365, give me a guest account and the work happens in your SharePoint. Your documents never leave your control, and your own retention and access rules apply the whole way through.
  • Otherwise — my environment. Microsoft 365 Business Premium under a signed data processing agreement, in a workspace restricted to your engagement, with multi-factor access and device controls turned on.
  • Your own AI licences. If you've already approved a particular platform internally, I'll use yours instead of mine. Just say so at scoping.
  • Platform. Extraction and analysis run on Claude Enterprise, under Anthropic's Commercial Terms. A business agreement, not a consumer account.
  • Training. Under those terms, customer inputs and outputs are excluded from model training by default. That's contractual, not a setting someone might leave switched on.
  • Deletion. Everything you give me, and everything I produce from it, is deleted at handover with written confirmation. I don't keep a copy for reference or reuse.
  • Personal data. Guarantor and contact details in lease documents don't get extracted unless configuration genuinely needs the field. Where it does, I act as processor on your written instruction.
  • Sub-processors. Anthropic and Microsoft. Nobody else without telling you in writing first.

I can attach a data processing addendum to any engagement letter. And if your security team would rather send a questionnaire, send it — I'd much rather answer it before scoping than after.

Lynne Muyano
Independent SAP RE-FX contractor · working remotely, any time zone
Book thirty minutes Or write to emailme@lynnemuyano.com · LinkedIn