Presentations P-00000 to P-00999

Presentations are filed by id. Start from the catalogue instead — by who you are, by module, or by learning path.

P-00001 — What LHDN expects each month
P-00002 — Consolidate the cash bills
P-00003 — Submit and watch the queue
P-00004 — Fix a rejection
P-00005 — Close the cycle
P-00006 — The 72-hour window
P-00007 — Cancel inside the window
P-00008 — Correct with a credit note
P-00009 — When a buyer rejects
P-00010 — Incoming supplier e-invoices
P-00011 — Reconcile a month with corrections in it
P-00012 — When a customer asks for an e-invoice
P-00013 — What happens to an ordinary cash sale
P-00014 — Take the buyer’s details at the till
P-00015 — The sale that is too big for the monthly batch
P-00016 — When the customer comes back
P-00017 — Which pool a document lands in
P-00018 — Read a pool row before you touch it
P-00019 — Clear the Individual Pool
P-00020 — Work the Batch Pool without stranding a receipt
P-00021 — The pool everyone forgets
P-00022 — What runs for you, and how you know
P-00023 — Find every rejection you have
P-00024 — Read the error and tell whose it is
P-00025 — The error families and the record behind each
P-00026 — Fix it at the source, not on the e-invoice
P-00027 — Resubmit, and prove it landed
P-00028 — What runs without you, and what never will
P-00029 — When a document will not go at all
P-00030 — Which customer records ever reach LHDN
P-00031 — The identity each kind of customer needs
P-00032 — The address BigLedger actually sends
P-00033 — Make a broken record impossible to save
P-00034 — Fix a whole book of customers at once
P-00035 — Let your customers key their own details
P-00036 — When the obligation is yours, not your supplier’s
P-00037 — Which documents can carry one, and how the flag gets set
P-00038 — Set the supplier up so it works
P-00039 — The blanks that divert it, and the blanks that let it go out wrong
P-00040 — What runs for you, and what never will
P-00041 — The traps, and proving the month
P-00042 — What you are reconciling, and what you are not
P-00043 — The list of purchases that should have one
P-00044 — What arrives, and what never will
P-00045 — Pair one by hand
P-00046 — Check the rest yourself, and clear the list
P-00047 — Which console your supplier’s invoice is in
P-00048 — What runs for you, and what month-end can prove
P-00049 — What you are asking for
P-00050 — Find your receipt
P-00051 — Give your details
P-00052 — Track it and download it
P-00053 — When something is wrong
P-00054 — Four records, and the order they come in
P-00055 — The chart comes before the company
P-00056 — Create the company, and what comes with it
P-00057 — Branches, and the location your stock lands in
P-00058 — Ledgers, a set of books and the fiscal year
P-00059 — The mapping that decides whether a document posts
P-00060 — Tax codes, cashbooks and the ways money moves
P-00061 — Finalise one document and prove it
P-00062 — Why one branch behaves differently from its siblings
P-00063 — Main Location, and where your stock actually lands
P-00064 — The branch settings your counter reads
P-00065 — What a branch prints, and what a branch is numbered
P-00066 — Locations: class, transit, and what runs for you
P-00067 — The branch settings that change nothing, and the two that do
P-00068 — Close a branch, and prove the settings
P-00069 — Two doors, and only one rings a bell
P-00070 — What one buyer’s request does to your month
P-00071 — Read the buyer’s screen before you answer
P-00072 — The complaints you will actually get
P-00073 — Open the door properly, and know when it closes
P-00074 — Whose sale is it to report?
P-00075 — Pick the level, and know what it costs
P-00076 — What happens behind the scene when you skip
P-00077 — Prove it at month end
P-00078 — How far the e-commerce reconciliation actually goes
P-00079 — Read the bill’s E-Invoice tab before you decide anything
P-00080 — The wrong number was keyed, and nothing stopped it
P-00081 — The customer wants their company on a bill they have already paid
P-00082 — Your after-Final tools, and which of them the e-invoice notices
P-00083 — The RM 10,000 bill: what the till stopped, and what it let through
P-00084 — What one receipt at your counter sets off
P-00085 — Why that sale went into the monthly batch
P-00086 — Is your branch a block on the e-invoice, or invisible inside one?
P-00087 — The sales LHDN never hears about from your branch
P-00088 — Close your branch’s month before the 1st
P-00089 — Your shop is three records, and only one of them is the shop
P-00090 — Why your till cannot find an item that is on your shelf
P-00091 — Why your prices and your totals are not the other shop’s
P-00092 — Where the money lands when you press Cash
P-00093 — The settings that reach you, the ones that stop at the company, and one that reaches nothing
P-00094 — Five ways a tax number lands on a record, and one that lands none
P-00095 — The registration the board has no number for
P-00096 — Invalid is three different things
P-00097 — Your suppliers are the half nobody counts
P-00098 — How you would know any of it happened
P-00099 — The three decisions that close behind you
P-00100 — What the item type decides in every other module
P-00101 — The two GL codes on an item, and which one your journal used
P-00102 — Where the cost on the Costings tab came from
P-00103 — Loading a catalogue without loading a mess
P-00104 — Nothing is rejected for a blank classification
P-00105 — Which of the three a late fix still reaches
P-00106 — The tenant default that nothing reads any more
P-00107 — Three lists, and the one that was never filled
P-00108 — Getting a catalogue ready, and proving it
P-00109 — The taxable type LHDN receives is arithmetic
P-00110 — One tax rate, four copies, and the one that charged
P-00111 — Tax Applicable is the switch, and most items have it off
P-00112 — Six rows in Tax Configuration that are not tax codes
P-00113 — Proving a tax setup from the only place that can prove it
P-00114 — One table, four ticks
P-00115 — The code you type is not the code that is stored
P-00116 — One record, one control account, decided once
P-00117 — The Tax tab on a customer is not where tax comes from
P-00118 — Merging repoints, it does not marry
P-00119 — A scheme is a label, the price is on the item
P-00120 — Which price list the document opened with
P-00121 — The tax on the line is not the price’s tax
P-00122 — A price row remembers the item as it was
P-00123 — The guard rails on a price, and which of them are real
P-00124 — Installing an applet is a door, not a fence
P-00125 — A target restricts documents, and not your customer list
P-00126 — Everything hangs off a role
P-00127 — Hiding a column is not withholding a number
P-00128 — What actually stops a sale below cost
P-00129 — One tenant, three companies, and the list they all share
P-00130 — A branch is where you traded; a location is where the stock is
P-00131 — Branch and profit centre are two columns, not two names
P-00132 — What Finalise does with your tags, and where it stops
P-00133 — Why your branch profit and loss does not foot
P-00134 — A price book is the layer that acts last
P-00135 — Which price set wins, and why the answer moves
P-00136 — When the book and the scheme disagree
P-00137 — Where the number came from, and what the line forgets
P-00138 — What a price book will not do
P-00139 — Finalise is a different button, and a different endpoint
P-00140 — One press, and a fan-out you did not configure
P-00141 — What the line remembers, and when it was remembered
P-00142 — Where the cost on your line came from
P-00143 — When the chain does not run, and how you find out
P-00144 — Four buttons, and only one of them is a void
P-00145 — Reversed, negated, removed: three kinds of undo in one press
P-00146 — Can your tenant unpost what it posts?
P-00147 — Undo to Draft is not a rewind
P-00148 — Which document wrote this cash book line
P-00149 — Every save rewrites the line, and the one edit the books refuse
P-00150 — Five ways a cash book line leaves, and only one of them is a void
P-00151 — Reading a reconciliation that moved under you
P-00152 — Process Request: what one click sets off, and what comes back
P-00153 — Four choices, and what each one tells LHDN
P-00154 — The clock, on both sides of 72 hours
P-00155 — How you will know: three records, and the check before you void a cash bill
P-00156 — Three things called a knock-off, and which number each one moves
P-00157 — Who writes the contra, and when the balance moves
P-00158 — What un-does a knock-off, and what each route leaves behind
P-00159 — Reading a knock-off that half-worked
P-00160 — What a consolidated e-invoice is made of, and what cancelling it does not touch
P-00161 — Four buttons, one missing column: why three cancellation choices do nothing here
P-00162 — Nobody is going to tell you: the e-mail, the queue and the report all read clean
P-00163 — Getting the receipts reported again, and asking for it in the right words
P-00164 — Three status columns on a Batch Pool row, and only one of them decides anything
P-00165 — The one month the consolidation run can see, and the months it cannot
P-00166 — The button that strands a row, and the guard that is only on its neighbour
P-00167 — Getting a stranded Batch Pool row back, and the four things that will not do it
P-00168 — The invoice you finalised is not the document that posts
P-00169 — Which rate, whose date, and which way round it is stored
P-00170 — Where the exchange difference lands when you knock the invoice off
P-00171 — Voiding a foreign-currency document, and reading the residue it leaves
P-00172 — Which LHDN your new company is actually talking to
P-00173 — The fields on a new company’s E-Invoice tab that switch something on, and the four that do not
P-00174 — Turning Peppol on for a new company, and the queue your document actually lands in
P-00175 — Proving a new company is live, and the four things that look like proof and are not
P-00176 — The moment you finalise a Peppol invoice, and what the Waiting Queue is not telling you
P-00177 — Who moves your invoice out of the Peppol Waiting Queue, and how often that actually happens
P-00178 — Reading To Peppol AP, Queue and History — what each Peppol screen is evidence of
P-00179 — Where a Peppol invoice stops, stop by stop, and who can restart it
P-00180 — Where the e-invoice PDF your customer receives comes from — the template, the logo, the address block and the QR
P-00181 — When the validated PDF is e-mailed, to whom, from what address — and the three things that must exist first
P-00182 — Reading the Email Dashboard and the e-mail thread — what a row is evidence of, and the rows that never move
P-00183 — Your customer’s PDF does not look like yours: the diagnosis, in the order that costs least
P-00184 — One tenant, three companies, twenty-two branches: where each e-invoice fact lives
P-00185 — Three registrations, one schedule: what setting e-invoice up three times actually means
P-00186 — The customer the whole group shares, and whose e-invoice it is
P-00187 — What a branch does and does not do to an e-invoice
P-00188 — The question the Discrepancies Report can answer, and the one it cannot
P-00189 — Where every number on the report comes from, and when it was read
P-00190 — What passes the report silently, and how you will know
P-00191 — Prove the month for a group: three companies, three reports, one routine
P-00192 — Whether Malaysia’s e-invoice rules apply to you yet, and what they ask
P-00193 — What goes on an e-invoice, and who fills in each part
P-00194 — The customer who does not want an e-invoice, and the sale that may not be consolidated
P-00195 — After LHDN answers: the 72 hours, and what stays your job
P-00196 — The portal your customer gave you, and what it will and will not show
P-00197 — What your customer ordered, and how much of it is still to come
P-00198 — How your invoice was matched to the goods receipt
P-00199 — When it does not agree, and the matching you cannot see