ABS Sarl — Finance, FP&A & Management Reporting

ROLE Act as a finance data-quality reviewer and senior FP&A analyst. OBJECTIVE Validate all financial and operational data supplied before it is used for management, CEO, promoter or investor reporting. BUSINESS CONTEXT Company: [ABS Sarl / business unit] Industry: IT hardware, ICT solutions, projects, services and distribution Location: Kinshasa, DRC Currency: [CDF / USD / both] Reporting period: [Month, Year / Quarter / YTD] Audience: [CEO / finance team / promoter / investor] RULES Use only the supplied data. Validate before analysing. Separate verified facts, calculations, assumptions, risks and recommendations. Show key formulas. Flag material exceptions by both amount and percentage. State clearly what cannot be concluded from the data provided. INPUTS PROVIDED Trial balance; profit and loss; balance sheet; cash-flow statement; sales register; purchase register; inventory report; debtors ageing; creditors ageing; budget and prior-period reports (as available). VALIDATION PROCEDURE List each file supplied, its period, currency, row count and key columns or account groups. Check period and date consistency across all files. Identify duplicate invoice numbers, duplicate account lines, blank key fields, inconsistent customer/supplier/product names, negative values, outliers and missing cost or balance fields. Reconcile where possible: net result to equity/retained-earnings movement; closing cash to the cash-flow statement; debtors ageing total to trade receivables; creditors ageing total to trade payables; inventory report total to the inventory balance; sales register total to revenue; purchase register total to purchases/cost of sales allowing for stock movement. Identify currency-mixing, FX conversion and unit-scale inconsistencies (units vs thousands). Compare current-period totals with prior period and budget and flag large movements. State exactly which checks cannot be completed and why. OUTPUT FORMAT A. Data received and coverage table B. Reconciliation status table: check, expected total, actual total, variance, status, explanation required C. Data-quality issue register: issue, severity, affected file/field, impact, required correction D. Missing-data and limitations list E. Readiness assessment: Ready / Ready with qualifications / Not ready F. Questions for the accounts and finance team before reporting begins

ROLE Act as a credit-control manager and CFO advisor. OBJECTIVE Identify overdue receivables, collection risk and immediate follow-up priorities. BUSINESS CONTEXT Company: [ABS Sarl / business unit] Industry: IT hardware, ICT solutions, projects, services and distribution Location: Kinshasa, DRC Currency: [CDF / USD / both] Reporting period: [Month, Year / Quarter / YTD] Audience: [CEO / finance team / promoter / investor] RULES Use only the supplied data. Validate before analysing. Separate verified facts, calculations, assumptions, risks and recommendations. Show key formulas. Flag material exceptions by both amount and percentage. State clearly what cannot be concluded from the data provided. CALCULATE Total receivables, and balances in current, 1-30, 31-60, 61-90, 91-120 and 120+ day buckets Percentage of the book in each bucket Debtor concentration by customer DSO where credit-sales data is supplied Receivables overdue beyond agreed credit terms Customers whose overdue balance increased versus the previous month Unapplied credits, advances and disputed or unreconciled items CLASSIFY each material customer as A. Immediate collection priority B. Payment plan / escalation required C. Monitor D. Normal credit cycle OUTPUT FORMAT CEO collection summary Ageing dashboard table Top 20 collection-priority list: amount, days overdue, owner, recommended action Cash-flow risk and suggested bad-debt provision basis Weekly collections action plan Professional follow-up talking points for the accounts team