ONEspace - PremierOne Group

Claims by expenses categoryRM, Amount only (TTP not included)

Category	This Month				Year to date
Category	OTX	P1TC	P1MC	Total	OTX	P1TC	P1MC	Total

Category breakdown

Year to date by staff

Claims by staffCMT is auto-approved · Director's own claims are under Director Claims

Month	CMT	HL	HW	AI	Total	Status	Action

New claim

Monthly claims

My claims by expenses category

Category breakdown

Claims recordsclick a month to open it

Month	TTP	Amount	Total	Last year	Status

- invoices

No	Inv No	Date	Client	PIC	SVCS	Fees	OPE	Subtotal	SST	Total	CR NOTE	Date Paid	OR No	FPC	O/S Bal	STATUSST

+ New Invoice

Yellow = required

Client

Client *

Entity * PIC *

Date *

Code (auto) Group (auto)

Invoice

Service * Fee kind

Professional fees * Out-of-pocket (OPE)

Subtotal

Service tax 8%

Total

Remark (optional; needed for a credit note whose reason is Other)

HP Schedule - hire-purchase instalments and interest

Do you need to amend, audit or verify the HP figure each month?

No monthly work, but check it against the bank at least once.

No monthly action: you type the agreement once. The app works out every month's interest and instalment, and “Shows Oct 2026” means each month it takes that month's figure automatically. The interest falls as the loan is paid down, and Standing Instruction follows without you touching it.
Check it once against the bank: the schedule is calculated by the Sum of Digits method (Rule of 78), not read from the bank's own statement. For SWE7993 the total interest (RM28,885) and ending balance (0) tie out exactly. It cannot be known that the bank rounds each month the same way.
1. When you next get a bank statement or amortisation letter for each car, compare one or two months' interest with the HP Schedule tab.
2. If they match, you are done until the agreement ends.
3. At year-end, compare the full-year interest with the bank's annual interest certificate. That is the figure that matters for the P&L and your tax computation.

Revenue & Banks Config

Entity	AR Collection Rate (%)	Invoice Rate (%)	Budget Outflow (RM/mo)

Revenue Budget Setup

Entity	2025 Total Actuals (RM)	Growth (%)	2026 Monthly Budget	2026 Annual Budget

📋 Advisor Note - Basis: % of Last Year Actuals (Incremental Budgeting)
Enter each entity's total professional fees billed in 2025 (from your Excel tracker), then set a target growth rate. The system computes a uniform monthly budget for 2026: Monthly = (2025 Actual × (1 + Growth%)) ÷ 12, applied across all 12 months and saved to the Revenue Dashboard automatically.

Why this method: For a professional services firm at PremierOne's stage, last year's billing is the most reliable anchor - it reflects actual client relationships, staff capacity, and market conditions. A growth rate of 10-15% is realistic for a growing tax practice (OTX). Use 0% or lower for P1TC (intern-only, limited capacity headroom) and P1MC (near-flat office management income). This method avoids over-optimistic budgets while still giving a meaningful variance target to track against monthly.

Override: To fine-tune individual months (e.g. March tax season peak), use the Revenue Dashboard's monthly entry form after applying here.

Loading staff records…

Loading payroll…

Yellow cells. You type these. Blue cells are automatic.
Blue cells. EPF, EIS, SOCSO and LINDUNG24 calculate from the Rates tab. Only PCB is typed.
Override. Type over a blue cell to replace it. An amber dot marks the change; click it to reset.
Source. Roster, position and gross pay come from HR Admin.

Expenses by Nature ▼ Show

Cashflow & Survival ▼ Show

Overview

This is the control room for ONEspace. Load data, check the invoice audit log, find the system links, and follow the setup guides.

Access. The Director sees all four tabs. A Manager sees Data tools only.

Data tools. Load or move records into this app: client fee history, principal activity and the Jan to Apr 2026 claims. Also the invoice audit log. Director and Manager.
Connected systems. The link, purpose and steps for each system the app uses: Netlify [where the live site is hosted], the live site, SharePoint, Azure and Microsoft 365. Director only.
User access. Who can open which module, and at which level. One open / close switch for each person and module. Director only.
Setup guides. How to install the PremierOne logo fonts, how to run the app on your computer in VS Code [the code editor used for testing], and the key terms in plain words. Director only.

1.1 📥 Import Client Fee History🟢 Safe to re-run+

1.2 ⚡ Migrate Principal Activity🟢 Safe to re-run+

1.4 📜 Audit Log - All Invoices · Last 200 entries+

2.1 Deployment Tools+

Site and link	Purpose	Steps
Netlify (Deploy) app.netlify.com/projects/onespace-premierone	Publish app updates to the live site.	1. Log in to Netlify. 2. Open this project page. 3. Drag the A\ONEspace\01_APP\publish folder onto the deploy drop zone. It holds Index.html and ONEspace.html and nothing else. Never drag the app folder. Netlify publishes every file you drop. The ONEspace folder around it holds data files and old copies. This is how staff records became public for months (S148). 4. Delete the previous deploy afterwards. A new deploy does not remove the old one.
Live ONEspace onespace.octagonace.com	The site you and staff use every day.	1. Open the link. 2. Sign in with your M365 work email. 3. Check that the dashboard loads.
SharePoint (Workspace site) octagonace.sharepoint.com/sites/workspace	The data store. It holds the Invoices, Claims and Clients records.	1. Open the link and sign in with M365. 2. Click "Site contents" on the left. 3. Open a list to view or edit its records.
Azure Portal (App Registration) portal.azure.com	Sign-in security: Client ID, Tenant ID and redirect URLs.	1. Sign in with your Director M365 account. 2. Type "App registrations" in the top search bar. 3. Open the ONEspace registration. Azure renamed it from "OpFinance" (S218).
Microsoft 365 Admin Center admin.microsoft.com	Staff accounts and licences. A new staff member needs one before they can sign in.	1. Sign in as admin. 2. Go to Users, then Active users (left sidebar). 3. Add or edit the staff account.

3.1 PremierOne Logo Fonts - Device Setup+

3.2 Working with VS Code+

3.3 Key terms in plain words+

The terms used when ONEspace is changed. Each one says what it is, why it matters, and what happens if it is skipped.

Putting changes live

Publish (also called deploy). Copying the newest ONEspace from the working computer to Netlify [the web host], so staff open the new version at the live address. Staff and CMT only ever see what is on Netlify. Once published, everyone sees the change at once, so the checks come first. If it is not published, staff keep the old version. A small change can wait. The risk of waiting is that many changes pile into one bigger publish, which is harder to check and to undo.

Commit. A saved, dated snapshot of all the project files, with a short label, kept in the project's history on the working computer. It lets any change be undone and shows what changed and when. Staff see nothing from it. If it is skipped, the work is not lost, but there is no restore point, so a later mistake could overwrite good work with no way back.

Where the data lives

SharePoint list. An online table in Microsoft 365, like an Excel sheet. Every client, invoice and claim is one row. This is the real data. The app only shows and edits it.

Permissions (list grants). Who may read or change each list. This, not the menus the app hides, is what keeps payroll away from staff. Permissions add up. A lower setting never takes one away. If a grant is wrong, staff could reach data that the menus only hide.

How the app reaches it

Sign-in and redirect address. The app signs you in through Microsoft [using MSAL, Microsoft's sign-in library]. Every web address the app runs from must be registered in Azure [Microsoft's app settings]. An address that is not registered gives a sign-in error such as AADSTS50011.

Graph. The Microsoft service the app uses to read and write the SharePoint lists. When a saved record looks wrong, its version history here shows who changed what, and when.

How the app is built and kept safe

Build. Joining many small source files into the one app file. Only the sources are edited, never the finished file. If the finished file is edited, the next build erases the edit.

Fingerprint (hash). A short code that changes if even one character changes, like a seal on a file. It proves the live site is exactly the version that was tested.

Snapshot and rollback. A copy of the app file saved before each rebuild, and going back to it. It is the undo button for the app file.

Read-back. Reading a record again from SharePoint after it is saved, instead of trusting the on-screen "saved" message. A save can be partial. The read-back proves it.

Localhost (test copy). Running the app on the working computer only, at http://localhost:5500/ONEspace.html, before anyone else sees it. It is a safe place to try a change. If it is skipped, staff become the first testers.

● Draft

Group cash

OTX cash

P1TC cash

P1MC cash

OTX transfer

UOB 8080 → 8226

P1TC transfer

→ 2004

P1MC transfer

CIMB 8962 → 1295

BANK CASHFLOW CONTROL	OTX					P1TC					P1MC
BANK CASHFLOW CONTROL	UOB			MBB	OTX	UOB	CIMB	MBB	PBB	P1TC	UOB	CIMB	P1MC
Account	8226	8080	UOB	8307	Total	1570	0304	6200	2004	Total	1295	8962	Total
Bank Opening Balance
− Last month's Batch 2
Cashflow Opening Balance
+ Incoming (pre-cycle)
= Funds per Bank Account
Step 1: Fund Transfer			-	-	-	-	-	-	-	-			-
Funds available for payment
⚠ Fund gap
− Payment : Batch 1
Cashflow Closing Balance Reconcile with bank stmt
+ Payment deferred − B2
Total Committed Payment (B1+B2)

Total Cash in Bank

Payment Journal - 25th Cycle

✔ Approved & Paid

OTX Total

RM 0

P1TC Total

RM 0

P1MC Total

RM 0

Grand Total

RM 0

25th Cycle 0 items

#	Date	Payee / Description	Amount (RM)	Status	Reconcile	Bank Account	Entity	Source / Expense	Ref

Batch 1 payment cells auto-compute from the Payment Journal once items exist. With no items, they stay manual entry. Approval workflow and Build-from-Claims arrive next.

Revenue & Collections

Item	OTX	P1TC	Tax Practice	Tax Practice (CY)	P1MC	Group	Group (CY)

Bank balances

Why this screen. The app has no link to the banks. Each month, the closing balance on every bank statement is read from the statement files (or typed) here, and the nine figures become the app's record of month-end bank balances, for reconciliation and future reference. They show the cash each entity holds and check Payment Advice: its expected closing balance should equal the bank. A difference means a receipt or payment was missed, or fell in another month.

What to do

1Download each account's statement for the month from the bank. Save it in A\ONEspace\04_DATA\Bank Stmt, in the entity's folder, named like CIMB 8962 - YYYY-MM.pdf. For UOB, download it from UOB's online banking rather than scanning the paper copy.
2 In the Windows box, open the Bank Stmt folder, type YYYY-MM in its search box, press Ctrl+A, then Open. Or drag the files onto this form. Each closing balance is checked against the statement's own totals before it fills a box; a figure marked ⚠ is typed by you after checking the statement. A blank box leaves that account as it is.
3Check the Difference column, then click Save balances.

Result

Action

Client

Invoice

Invoice

Payments

Record payment

Bank balances