How To Make Intercompany/Inter Fund Management Easy Extending Sage ERP Accpac
Introduction Inter Entity Transactions NEW Cash Management NEW GL Triggers
NEW IY TRADE Module Questions
Agenda
Based in Sydney, Australia Sage 300 ERP (Accpac) Solution Provider for over 15
Years Working with the Accpac SDK since 1996 Development Team includes 5 programmers with
combined development experience of over 70 years Represented in North America by Robert Lavery &
Associates Awards include:
2012 & 2011 Gold Development Partner of the Year ACCPAC International Development Partner Rising Star ACCPAC Australia Development Partner of the Year ACCPAC Australia Solution Provider of the Year Sage CRM Australian Solution Provider of the Year
Who are Orchid ?
Orchid’s Technology
All products developed 100% in the ACCPAC SDK Standard ACCPAC Security and Customization capabilities Data integrity checking Client Server and Web deployment Support for all Databases DBDump and DBLoad Macro support with VBA ACCPAC look and feel Crystal Reports
Well suited to non-profit organizations with Fund Accounting requirements
Companies with Inter Company Transactions Companies requiring Branch or Divisional
Accounting Any organization with loan accounts which should
mirror each other as a result of inter divisional / inter company held within one or across multiple ACCPAC databases
Inter Entity Transactions
Reduce Errors & Increase the accuracy of your financial data Streamline business processes while
saving keystrokes and time Tighten control over transactions
spanning multiple entities (incl. branches, divisions, funds, projects, trusts or multiple companies held within one or across ACCPAC databases)
Inter Entity Transactions – Key Benefits
Due To / Due From transactions generated automatically (balanced at a GL Segment level)
Complex routes can be followed Keep each entity in balance automatically Log maintained to manage transactions flowing
across databases Supports groups with differing financial periods
and different currency GL’s Works on all GL transactions regardless of their
origin: GL entry, subsidiary ledger, a third party module or an external system
Inter Entity Transactions
2 Versions are available: Single Database – Operates
within one ACCPAC company database
Multi Database – Operates across multiple ACCPAC company databases. (The databases can reside on the same server and/or can be remote.)
Entity 1 SAMLTD – Division 1
Entity 2 SAMINC - Company
Entity 3 SAMLTD – Division 3
Entity 4 REMOTE - Company
Inter Entity Transactions
Manages Cash (Bank) Transfers through Bank Services to record on Bank Reconciliation
Manages AR Receipts and AP Payments made on behalf of related companies (One Step Process)
Transfers of AR/AP Invoices to a management company for consolidated receipt or payment processing (Two Step Process) to keep each entity in balance automatically
Consolidated AR and AP Aging Report Log maintained to manage transactions flowing
across databases
Inter Entity Transactions – Cash Mgmt
GL Offset: Allows you to code a transaction to an Account in your Chart of Accounts (Source Company) and map it to another Account in the Target Company OR
GL Entity Substitution: to another Account and an Optional Field for the Entity to map to an Account in multiple Target companies.
AP/AR Offset: Can code a GL transaction to trigger an entry to an AP Vendor or AR Customer in the same company database.
Log maintained to manage transactions flowing across databases
Inter Entity Transactions – GL Triggers
Generates Buy/Sell Transactions between related companies – AR and AP & OE and PO
Manages AR AP Invoices and Credit Notes as well as OE PO Orders, Shipments/Receipts and Invoices.
Item Mapping Table if Item Numbers are different Can identify Intercompany profits (Sales versus Cost
of Sales) using the IC Category override feature Log maintained to manage transactions flowing
across databases Support for Lot & Serial Numbers, PJC Contracts
and IC Stock Transfers is next
Inter Entity Transactions – TRADE
Next Steps
Speak with your Sage Business Partner Attend an Orchid Systems webinar Request a one-on-one web presentation
•Business Intelligence represents the tools and systems that play a key role in the strategic planning process of an organization. •Information Manager
• Report Runner • Supplementary Data • Notes • Data Views – simplify reporting on optional fields
• Document Management Link **NEW**
• Info-Explorer
• Process Scheduler
Information Manager| What is BI ?
Presenter: Robert Lavery
• Menu of Crystal reports: • Accpac’s • Own Crystal Reports
• Define parameters – including Accpac finder, period picker, date picker
• 26 Security Groups – assign to reports/users
• Only available reports visible
• Run, view, print, e-mail • Schedule using Process Scheduler
Information Manager| Report Runner - Crystal Reports
• Menus of FR reports
• Define parameters • Run, view, print, e-mail • Schedule using Process Scheduler
Information Manager| Report Runner - Financial Reports
Process Scheduler | Automation
• Schedule Report Runner Crystal Reports (L1)
• Schedule Report Runner Financial Reports (L3) • Schedule Info Explorer Cubes (L1)
Schedule (L1): • Data Integrity
Checks • Dump DB • Service Pack Audit • Clear Integrity Logs
Schedule (L2):
• Day End • Post batches
Schedule (L3):
• Load/Copy DB • GL Cons Export • GL Cons Import • Run VBA macro • Run external
program
• Add-in from Excel to maintain infoset data • Report using Info-Explorer
• Maintain links to external documents & view from within Accpac
Information Manager| Supplementary Data
• Create own infosets
• Enter/Import/Export data
For Unstructured notes :
• Multiple note types • Security per roles & note
types • Configured per screen/field
or field • Configure to pop up on any
field except • field in a grid • Drop down boxes/check
boxes • Define default colours for
notes – with override
For Structured notes : • Configured per screen/field
or field • Configure to pop up on any
field except • field in a grid • Drop down boxes/check
boxes
Information Manager| Notes
• Unstructured data : Free format note box – as long as you want
• Structured data : list of optional fields
For SharePoint Documents: • Open documents from
Accpac • Insert documents from
Accpac (Links Added) • Set a filter on the document
directory • Use SharePoint Security • Trigger SharePoint Workflow
For File Share Documents : • Open documents from
Accpac • Insert documents from
Accpac (Links Added)
Document Management Link| shown with IM Notes
• Documents stored in SharePoint
• Documents stored on a file share
Info Explorer| Data Views
• Automates Database View creation to “flatten” Accpac Optional field structure
• Simplifies & improves performance of Info-Explorer queries • Simplifies & improves performance of Crystal Reporting
• Text is stored in the database – so will dump and load. Easy to re-create the views
• Provides documentation on sites
InfoExplorer| Analysis
Info- Explorer is good for Operational Analytics · Can drill down into underlying Accpac screens · More cost effective than creating multiple Crystal Reports · Can easily access other databases
How To Make Securing Assets & Data In Sage 300 ERP (Accpac) A Snap
Norming Software International Ltd.
Norming Solutions that Secure Data
Bank Security: Control which users can see or use certain Banks based on permission settings. AR Security: Control user access to Customers, Price Lists, AR Sales History, based on permission settings. AP Security: Control user access to Vendors, AP Purchase History, based on permission settings. Inventory Security: Control user access to IC items and locations, based on permission settings. Purchase Security: Control user access to Vendors, AP invoice/payment, purchase order and purchase history, based on vendor group permission settings. Sales Security: Control user access to Customers, Price Lists, Order Entry, Sales History, based on permission settings.
Bank Security – Banking Access Restrictions Bank Look Up, Inquiry and Transactions: Users can’t look up restricted banks or perform inquiries on data and transactions in BS, AR & AP.
Adding new Banks: Users can add new banks within a restricted range but can’t view the new bank. Posting Batches: Posting is limited to batches that do not contain restricted banks. Can’t view a batch with restricted banks as the batch will not appear in the Batch List window. Payment & Receipt Entry: Users can not enter or view payment or receipt entries for restricted banks in AP & AR. Import & Export of Bank Data: Users can not import and export data for restricted banks. Apply Bank Restrictions in Bank, AP & AR Reports: (Sample - BK1410.RPT) Bank Security maintains a bank permission table (BSUSERD) to define user access to banks. You can include this table in any Accpac reports to apply security control in Bank, AP or AR Reports.
AR Security – Customer Access Restrictions
Customer Look Up, Inquiry and Transactions: Users can’t look up restricted customers or perform inquiries on data and transactions in AR.
Adding new Customers: Users can add new customers within a restricted range but can’t view the new customer. Posting Batches: Posting is limited to batches that do not contain restricted customers. Invoice & Receipt Entry: Users can not enter or view invoice or receipt entries for restricted customers in AR. Import & Export of Customer Data: Users can not import and export data for restricted customers. Apply Customer Restrictions in AR Reports: (Sample – ARCULT01.RPT) AR Security maintains a customer permission table (AQUSERD) to define user access to customers. You can include this table in any Accpac reports to apply security control in AR Reports.
AP Security – Vendor Access Restrictions
Vendor Look Up, Inquiry and Transactions: Users can’t look up restricted vendors or perform inquiries on data and transactions in AP.
Adding new Vendors: Users can add new vendors within a restricted range but can’t view the new vendor. Posting Batches: Posting is limited to batches that do not contain restricted vendors. Invoice & Payment Entry: Users can not enter or view invoice or payment entries for restricted vendors in AP. Import & Export of Vendor Data: Users can not import and export data for restricted vendors. Apply Vendor Restrictions in AP Reports: (Sample – APCULT01.RPT) APSecurity maintains a vendor permission table (VSUSERD) to define user access to vendors. You can include this table in any Accpac reports to apply security control in AP Reports.
Inventory Security – Item/Location Access Restrictions
Item & Location Look Up, Inquiry and Transactions: Users can’t look up restricted Items & Locations or perform inquiries on data and transactions in IC, OE & PO. Items can be restricted by Item, Category or Account Set. (Not simultaneously.) Adding new Items & Locations: Users can add new Items/Locations within a restricted range but can’t view the new Items/Loc. IC Receipt, Shipment, Internal Usage, Adjustments, Transfers, Assemblies Entry: Users can not enter or view any IC entries for restricted Items & Locations in IC. Import & Export of Item & Locations Data: Users can not import and export data for restricted Items & Locations. Apply Item & Location Restrictions in IC Reports: (Sample – ICITMST1.RPT & ICLOC01.RPT) IC Security maintains a Item/Location permission table (ISUSERDI) to define user access to Items/Locs. You can include this table in any Accpac reports to apply security control in IC Reports.
Purchase Security – Vendor Access Restrictions
Vendor Look Up, Inquiry and Purchase History Transactions: Users can’t look up restricted vendors or perform inquiries on data and transactions in AP & PO. Vendors can be restricted by Vendor, Vendor Group or Account Set. (Not simultaneously.)
Adding new Vendors: Users can add new vendors within a restricted range but can’t view the new vendor. Entry & Posting of PO Order, Receipt, Returns & PO/AP Invoice, Credit/Debit Note Batches: Users can not enter, view and post PO Orders, Receipts, Returns, PO/AP invoice, Credit/Debit Note entries for restricted vendors in AP & PO. Import & Export of Vendor Data: Users can not import and export data for restricted vendors. Can Control Which Users Can Access PO Requisition with Blank Vendor Apply Vendor Restrictions in AP Reports: (Sample – APVENLT01.RPT) PO Security maintains a vendor permission table (PSUSERD) to define user access to vendors. You can include this table in any Accpac reports to apply security control in AP Reports.
Sales Security – Customer Access Restrictions Customer & Price List Look Up, Inquiry and Sales History Transactions: Users can’t look up restricted customers & price lists or perform inquiries on transactions in AR & OE. Customers can be restricted by Customer, Customer Group or Account Set. (Not simultaneously.)
Adding new Customers & Price Lists: Users can add new customers & price lists within a restricted range but can’t view the new customer & price list. Entry & Posting of OE Order, OE/IC Shipment, Credit/Debit Note & OE/AR Invoice, Batches: Users can not enter, view and post OE Orders, Shipments, Credit/Debit Notes, OE/AR invoices, entries for restricted customers & price lists in AR, IC & OE Import & Export of Customer & Price List Data: Users can not import and export data for restricted customers & price lists. Apply Customer & Price List Restrictions in AR/OE/IC Reports: (Sample – ARCULT01.RPT) Sales Security maintains a customer/price list permission table (SSUSERDC) to define user access. You can include this table in any Accpac reports to apply security control in AR, OE, IC Reports.