ec-g2
- accounting
- OpenACS
- Accounts Desk
- Accounts Finance
- Accounts Ledger (General Ledger)
- Accounts Payables
- Accounts Payroll
- Accounts Receivables
- Application Neutral Audit (ANA) Logs
- Bulk Upload
- Customer Service
- ECKS Forms
- ECKS templates
- Ecommerce-2
- Ecommerce-g2
- Ecommerce-g2 development guidelines
- Ecommerce-g2 package list
- Ecommerce-g2 requirements
- Fabrication
- Field Service
- Glossary
- Human Resources
- Inventory Control
- Manufacturing Design
- Online Catalog
- Production
- Reference Data - GIFI
- Reference Data - UNSPSC
- Shipping Tracking
- Spreadsheet
- Supply Chain
- Systems simulator package
- Task: add locales (done)
- ec-g2 contributors
- other non-OpenACS software
in last 20 minutes
Accounts Receivables
Vision Statement
Accounts Receivables provides, manages and tracks quotes, sales orders, invoices and their payments, refunds etc. And provides a web-based interface for related services to other packages including shopping basket functionality for ecommerce.
Requirements
- port from sql-ledger as a base
- able to import sql-ledger database
- 3 contacts per invoice (see Feature Request number 8).
Implementation Notes
Consider combining/normalizing the AP/AR/GL tables to one GL table to simplify the sql etc. in so far as they are essentially variations on the same table. The separate AP/AR tables will only handle data that are unique to each class of transaction grouping.
Feature requests
1. This package should be able to display/modify an order, such as "claim a gift-certificate" and "choose a shipping method" which are functional components of an ecommerce shopping-basket. (This feature moved from Bug 2397 on OpenACS.org
2. RECOVER FROM LOST SHOPPING BASKETS - Not very repeatable, but here's the case: User adds some items in the shopping cart. browser crashes/munges session_id or openacs creates a new session_id as the result of some other trigger. Shopping cart appears empty to the user.
There should be a way for logged-in users to be able to retrieve a shopping basket that has not yet expired or been saved. Maybe after seeing that a user is logged in and has an empty basket, list any unexpired shopping baskets that the user has, as a "Here's your recent shopping basket history", perhaps by directing user to their account area if a history exists. The system could then list this feature as a benefit to users who register. (This request moved from Bug 2337 on OpenACS.org)
3. UNREGISTERED USER PURCHASES - Add the ability for anonymous or "unregistered" users to make an order without registering first. (from OpenACS bug number 2299) Here's my thought for workflow at this point:
- When user views shopping basket, the system offers registration perhaps with possibility they may qualify for a lower price once registered.
- If user is not registered prior to checkout, then buyer is directed to a checkout-one-form-add-user page.
- no prior history is checked for filling form default values
- a new user is created using buyers name and phone or something as the account name
- user should be offered two choices. 1. auto-registration from info provided, or 2. a checkbox to not have ability to sign in to this account --in case user is ulta-paranoid and does not want info accessible via web. How to do this? no password? random password? set a user-account state? Once order is authorized, the paranoid user would have to be automatically logged out --or the order self destructs =)
- an email address is optional --sends order status notifications if available (and doesn't break ec if not).
4. UI for sales or others to build a quote or add to (or make a fresh copy?) someone else's shopping basket who calls in etc. and either complete fulfillment or save quote in user's shopping-cart (from OpenACS.org Bug 1656)
5. UI for sales or others to add some additional items not in the catalog db (and make a manage "new items list" so managers/admins can complete the data and publish new items, or erase/let expire as unique etc. (from OpenACS.org Bug 1656)
6. wrap the quote in a templated letter (from OpenACS.org Bug 1656)
7. optionally email quotes, auto register quote with new user (if a new user) and save quote in user's "saved baskets" area, and put a note in the customer service history (which means that the quote should include an option to use a template-based email letter. (from OpenACS.org Bug 1656)
8. have ability to summarize multiple customer records as one for AR aging/billing report. Use case: Sometimes regional fulfillment centers (which have their own contact record) make orders that the head office pays for. SL has 2 contacts for invoicing (Orderby/Bill to and Ship to), whereas ecommerce has 3: order-by, bill-to, ship-to. Using 3 contacts per invoice nullifies this request.
9. a place to store internal notes as order moves from quote to fulfillment and any returns info, such as RMA numbers