Search options (Page 2 of 11)

For a non-jquery approach, see this commit in my fork.

Have you tried prepayments?

The error message means what it says, that the reference already exists on some other transaction.

I have seen this in vanilla FA when multiple browser tabs are opened on bank payments.  If this is the case, then the solution is simple.  Only display one bank transaction at a time; do not use another browser window to examine any other transaction before completing the edit of that transaction.

Otherwise the problem is that you have duplicate reference numbers.

If the date is used in the reference number, and you change the date, bingo, that is the problem.  Note that is OK if the year is part of the reference number if only the month or day is changed.

If the date is not used in the reference number, then you need to examine the database with a tool such as the mysql client and search for the reference number in the database to confirm if duplicate reference numbers exist in the database.

Vanilla FA quietly unreconciles an edited bank transaction.  The code fix for that is in my fork.

Use General Journal Processing, e.g.

000001/99,03/28/1998,"Bank Account 1:Funds Transfer",-500.00,3300,,,,,,
000001/99,03/28/1998,"Bank Account 2:Funds Transfer",500.00,1060,,,,,,

@apmuthu:  This function is in my osCommerce and Square extensions.  These extensions import sales orders into FA, which is the same purpose as Import Transactions -> Sales Orders.  The function retrieves the FA sales point by name suitable for populating $cart->pos, which allows an order to specify the bank account for a direct invoice payment.

The function isn't necessary.   The core provides get_sales_point($id) (sales/includes/db/sales_points_db.inc) which can be used to populate $cart->pos, if you know the mysql key to the sales point.   The function that I suggested allows the sales point to be retrieved by name rather than id.

Import Transactions -> Sales Orders does not have the ability to specify multiple sales points and neither does the core.  By design, the core relies on a single POS per user.  All user transactions use this POS.  To me, that design seems rather inflexible, and discussions about changing that design have not been well received.

Therefore, customization is required to pick and choose multiple sales points when running under a single user.  Import Transactions -> Sales Order could be customized by adding a sales point field (id or name) to the import file and then in the code setting $cart->pos = get_sales_point($id) or $cart->pos = get_sales_point_by_name($name).

FA limits direct customer sales invoices to cash accounts.  This is because Setup->Points Of Sales->Default Cash Account is limited to cash accounts.  This is easily overridden with the code change:

--- a/core/sales/manage/sales_points.php
+++ b/core/sales/manage/sales_points.php
@@ -130,7 +130,11 @@ text_row_ex(_("Point of Sale Name").':', 'name', 20, 30);
 if($cash) {
        check_row(_('Allowed credit sale terms selection:'), 'credit', check_value('credit_sale'));
        check_row(_('Allowed cash sale terms selection:'), 'cash',  check_value('cash_sale'));
-       cash_accounts_list_row(_("Default cash account").':', 'account');
+
+        // POS systems often allow direct deposit into bank accounts,
+        // so do not restrict the POS "cash sale" to cash accounts
+       // cash_accounts_list_row(_("Default cash account").':', 'account');
+       bank_accounts_list_row(_("Default account").':', 'account');
 } else {
        hidden('credit', 1);
        hidden('account', 0);

By making this code change, a pos can be created with a non-cash account.   Then use Setup->User Accounts Setup to create a user with this POS.  Then try import transactions using this user.

I do not know if this will work, but it may get you further than before.

I do know that the rest of FA tolerates this change because my site uses this.  But I do not use Import Transactions for this purpose.

Sales orders are canceled, not voided.  You can use Sales->Sales Order Inquiry to see the sales orders, select a sales order, edit, and cancel.

Of course that raises the question, "How do I find the sales order that uses the item?".  You might need to examine the database to find it.

I realize that this is an old topic, but I've just wiki-ed the following procedure to edit Direct Supplier Invoices:

    1. First void the invoice (Setup->Void A Transaction)
    2. Void the delivery.  Note that the delivery cannot be voided until the invoice is voided.
    3. Purchases->Outstanding purchase orders maintenance: Edit the PO.  You can change date, add or remove items.
    4. Purchases->Outstanding purchase orders maintenance: Receive the PO
    5. Purchases→Supplier Invoices: Invoice the PO

Presently you can do this by item by setting the item's Inventory Adjustments Account.  Perhaps set all manufactured items to use waste and shrinkage instead of purchase price variance.  But if you want to use more than one account per item and then pick and choose when you make the adjustment, you will have to change the code.

If there is a problem with the latest 2.4.8 FA code base and not with an earlier FA code base, that would suggest that a recent commit introduced the problem.  You could try to isolate the problem by checking out successive earlier versions until you find one that works.

After you enter an invoice, what does view the g/l entries from this invoice look like?  Does that look correct?

I am sorry I cannot be of more help right now.

Thats a good question and it looks like the decision has been made to add dimensions to A/R and A/P in FA in 2.4.8.     In my fork, all G/L entries including A/R, A/P, taxes, discounts, etc all have dimensions if the invoice is assigned a dimension.  Its the only way to get an accurate P/L by dimension.

Go to this order on the FA demo site.

1. Does this page look like your page?
2. Change the date to 12/31/2019 (so that it is in the correct fiscal year).
3.. Press Process Receive Items.  Did it work?

If this works on the demo site and not your site, then there is some code or data difference that is preventing it from working on your site.

(Note: this can only be tested once.  To test multiple times, enter a new purchase order and try again).