Freelancers using Excel VBAFreelancers using Excel VBA
Delivering a pro job is a must
$50k+
Earned
1x
Hired
5.0
Rating
13
Followers
Delivering a pro job is a must
I fix warehouse chaos SOPs, SAP & Excel system for ops team
5.0
Rating
8
Followers
I fix warehouse chaos SOPs, SAP & Excel system for ops team
Cover image for Most warehouse audits I've seen
Most warehouse audits I've seen focus on the wrong things first. Neat labels, clean floors, a binder full of SOPs nobody's opened in months — all of it can look great and still sit on top of a warehouse that's quietly bleeding money. And the SOP binder is usually worse than just outdated. Somewhere along the way, the actual process changed — someone found a faster way to do something, or worked around a problem — and that change lived in their head, not in the document. Everyone just adapts and moves on. Then that person leaves, and suddenly nobody can explain why the process works the way it does, because the only place it was ever really "written down" walked out the door. If I only had fifteen minutes to walk a warehouse, here's honestly what I'd check. I'd skip the month-end accuracy report and ask what's mismatched right now, today. A clean number at month-end really just tells you how good someone is at patching things up before a deadline. Asking about today tells you whether the process actually holds up when nobody's paying special attention to it. Then I'd go find one picker and just watch them complete one real order, start to finish — not a demo, an actual order in the middle of a shift. You learn more in five minutes of watching someone walk a pick path than you do in an hour of reading reports. How far they're walking, how often they double back, how many times they have to stop and ask someone where something actually is. I'd also want to know how long stock sits between receiving and put-away. Not how fast it gets scanned in — how long it physically sits on the dock before it's properly stored. That gap, more than almost anything else, is where damage, shrinkage, and "we can't find it" problems quietly start. And I'd ask a warehouse worker why something's done a certain way — not a supervisor. If the answer is "that's just how we've always done it," that's usually a process nobody's questioned in years, or worse, a workaround that only exists in that one person's head. Last thing, I'd look at what's actually sitting near the exit versus what's actually fast-moving. Layouts get set once and almost never revisited. More often than you'd think, the stuff people grab constantly is buried in the back, and something nobody's touched in months is sitting right up front for reasons nobody remembers anymore. None of this needs a clipboard or a formal audit template. It just needs fifteen minutes and being willing to ask "why" one more time than feels comfortable — because the answer might only exist in one person's head, and that's the real audit finding.
0
39
Cover image for Why your SAP data is
Why your SAP data is inaccurate — and it's not SAP's fault. Every time someone tells me "our SAP data is a mess," I ask a few questions, and almost every single time, the answer has nothing to do with SAP. The system did exactly what it was told, exactly when it was told. If the number on screen doesn't match what's actually on the shelf, something happened on the floor that never made it into the system — or it made it in late, or someone found a shortcut because doing it properly during a busy shift felt like a luxury nobody had time for. Picture this: the shelf says 40. SAP says 42. Nobody's lying — the count on screen is just repeating something that was entered wrong, or late, or never corrected. I've seen the same handful of patterns show up again and again, at different sites, with completely different teams. Someone unloads a truck, and the goods receipt doesn't get posted until hours later because paperwork felt like it could wait until things calmed down. By the time it's finally entered, nobody actually remembers if it was 40 units or 42 — so whatever gets typed in is really just a best guess dressed up as data. Or transactions get batched at the end of a shift instead of logged as they happen. The timestamps look fine, but the actual sequence of events is gone, which means when something doesn't match later, there's no way to trace back what caused it. Or someone just overrides the number to make it "correct" for now, without asking why it was wrong in the first place. That fixes the symptom for exactly one day. The actual cause is still sitting there, waiting to cause the same problem next week. And honestly, a lot of training doesn't help either — people get taught which buttons to press, but nobody explains why the timing or the order of steps actually matters. So they follow the steps, but they have no idea what breaks the moment one gets skipped. None of this ever shows up as a system error. It just shows up as "SAP's wrong again," which is usually the one explanation that isn't actually true. The fix is almost never a system change. It's a behavior change — closing the gap between the moment something physically happens and the moment it gets recorded, and making the right way to log it the easy way instead of the slow one. If your numbers keep drifting from reality, the system isn't lying to you. It's just repeating exactly what it was told.
0
109
Cover image for I spent the first couple
I spent the first couple of years treating inventory accuracy like a fire drill. Count everything the week before month-end, patch whatever didn't match, submit the report, forget about it until next month. It worked, technically. Once. Then the small gaps started piling up faster than I could explain them. What actually changed things wasn't a new tool or a new SOP. It was realizing IRA isn't something you report on — it's something you either protect every day or you don't. Every goods receipt, every issue, every transfer is a moment where the system and the actual shelf can quietly drift apart. Catch that drift the same day and it's a two-minute fix. Let it sit for three weeks and it turns into a full investigation, and usually nobody remembers what actually happened. A few things I've genuinely stuck to since then: Reconcile the same day, not at month-end. I know it sounds obvious written down, but most warehouses don't actually do this — batching corrections is just easier in the moment. Let SAP flag mismatches early instead of waiting for someone to physically count and notice. The system usually knows before the floor does. Ask what kind of discrepancy it is before writing it off — receiving error, system delay, handling mistake. They all look the same on a report and none of them are fixed the same way. Whoever touched the transaction is the one who catches the error. Not an audit team three weeks later going through paperwork. None of this is glamorous. It's mostly just refusing to let small things wait. But it's the reason we held 100% month-end IRA consistently, and it's also the reason the number actually meant something when auditors came through — not just a figure that looked clean on a slide. If there's one thing 7 years taught me, it's that inventory accuracy was never really about the count. It was about how disciplined the process stayed on the days nobody was watching. #InventoryManagement #SupplyChain #FMCG
0
77
Accounting & Finance Automation | Excel & VBA
New to Contra
Accounting & Finance Automation | Excel & VBA
Engineering FP&A systems with custom AI Logic
Engineering FP&A systems with custom AI Logic
Helping Businesses Grow Through Accounting
Helping Businesses Grow Through Accounting
Cover image for Title: Automatic Bookkeeping Workbook —
Title: Automatic Bookkeeping Workbook — Single-Entry Journal to Full Financial Statements Description: A lightweight, fully automated Excel bookkeeping template built around one core idea: type a transaction once, and every downstream report updates itself. Unlike a full client engagement model, this is designed as a clean, reusable template — enter journal entries as balanced debit/credit lines on the one editable sheet, and the workbook handles the rest automatically: 1.One input sheet: Journal Entries is the only tab you type in — pick accounts from a dropdown, enter debit or credit amounts, and a built-in check column flags instantly if a line doesn't balance 2.Automated General Ledger: every account's full transaction history and running balance, generated without a single manual formula 3.Trial Balance with a live balance check 4.Financial statements: Income Statement, Balance Sheet (with automatic balance verification), and a direct-method Cash Flow Statement — all driven off a Cash Flow Category tag on cash transactions 5.Dashboard: auto-generated KPI snapshot (Total Assets, Liabilities, Equity, Net Income, Ending Cash) plus Revenue vs. Expenses and Operating Expense Mix charts 6.Color-coded design: blue for inputs, black for same-sheet formulas, green for cross-sheet links, grey for automated helper columns — so anyone opening the file immediately understands what's safe to edit Built to show that solid double-entry bookkeeping logic can be made genuinely foolproof for a non-accountant user — no VBA, no macros, just clean formula architecture. Skills demonstrated: Excel automation · Double-entry bookkeeping · Template design · Data validation · Financial statement preparation · Dashboard & chart design
1
122
Cover image for Startup Financial Model — 3-Year
Startup Financial Model — 3-Year Excel Model for Early-Stage Businesses A complete, investor-ready financial model built for newly established businesses, delivered as a fully dynamic Excel workbook (9 linked tabs, 685+ live formulas, zero hardcoded outputs). What's included: 1.Startup Costs — itemized pre-launch capital requirements with contingency buffer 2.Revenue Build — multi-stream revenue modeling with monthly detail for Year 1 and 3-year projections 3.Operating Expenses — fully categorized cost structure with annual escalation 4.Break-Even Analysis — automated contribution margin, break-even point, and margin of safety, with a visual chart 5.3-Year P&L Forecast — full income statement from revenue down to net income, monthly + annual 6.Cash Flow & Cash Requirement — monthly runway analysis with receivables/payables timing, pinpointing exactly when and how much additional cash is needed 7.Funding Requirement — Sources & Uses summary that ties out automatically, producing a clear capital ask Why it stands out: Every number is a live formula, not a static output — change one assumption and the entire model (break-even, forecast, cash runway, funding ask) recalculates instantly Color-coded inputs (blue), formulas (black), and cross-sheet links (green) so any user can navigate and edit safely Built to professional modeling standards — clean formatting, documented assumptions, verified formula integrity Ideal for: founders raising a pre-seed/seed round, small business owners applying for a loan, or accelerator/incubator applicants who need a credible, lender/investor-facing financial model fast.
1
115
Cover image for Forward Sports (Pvt.) Ltd —
Forward Sports (Pvt.) Ltd — Dynamic 5-Year Three-Statement Financial Model A fully-linked, scenario-driven financial model built in Excel for Forward Sports (Pvt.) Ltd, a Sialkot, Pakistan–based sporting goods manufacturer and exporter — forecasting FY2026–FY2030 off a FY2025 actual base year. Scope of work: 1.Scenario-Driven Assumptions — built a live scenario switch (Base / Upside / Downside) driving revenue growth (3%–13%) and COGS as a % of revenue (59%–64%) through OFFSET + MATCH formulas, so the entire model recalculates from a single dropdown input 2.Operating Expense Build-Up — modeled SG&A, R&D, and Marketing as % of revenue over the forecast period, feeding directly into the income statement 3.Income Statement — fully linked 6-year P&L (2025A–2030F) from revenue through COGS, gross profit, operating expenses, and net income, all formula-driven off the assumptions tab 4.Balance Sheet — dynamic 5-year balance sheet with automatic balance checks tying back to the income statement and cash flow 5.Cash Flow Statement — indirect-method cash flow statement (CFO/CFI/CFF), reconciling net income to the change in cash and linking to the Balance Sheet 6.Ratios & Summary — a KPI panel with margin, efficiency, and return ratios, plus SUMIFS-based period totals for revenue, net income, and marketing spend 7.Dashboard — a forecast-summary dashboard with a scenario selector and revenue/net income/EBITDA-margin charts (Base case: ~19% EBITDA margin through the forecast, Net Income growing from ~$5.0M to $5.8M FY2026F–FY2028F) Why it matters: Every figure flows from a single set of assumptions — change the active scenario and the entire model, from the P&L down to the dashboard chart, updates automatically. Nothing is hardcoded, which is exactly what makes it defensible in front of a client or professor. Skills demonstrated: Financial modeling · Three-statement integration · Scenario/sensitivity analysis · Advanced Excel (OFFSET, MATCH, SUMIFS, dynamic named ranges) · Dashboard design · Forecasting
1
80
E-Commerce & Marketplace Consultant | Amazon · Shopify · D2C
New to Contra
E-Commerce & Marketplace Consultant | Amazon · Shopify · D2C